You can run a command line from a job step. Getting the command line to report back a failure properly and give you any useful information would require you actually write out back to the console from your assembly - assuming you have done this, it should work fine.
If you already have everything written in VB.Net, you could also copy and paste your code and create a CLR stored procedure. You may have to enable unsafe assemblies, but it would allow you to run your reports as stored procedures directly in T-SQL.