I'll potentially be doing hundreds of these calls in parallel and I have to avoid the overhead of shelling out every time. I've already tested and the difference is very significant when opening to ssh vs opening to a shell opening to ssh. There's a huge slowdown on the local machine when I involve the shell.
A mistake can be valuable or costly, depending on how faithfully you pursue correction
Store the string in the database with some token that you can split on, that won't show up in the command itself. But, the "||" in your example is a shell operation, it won't work in 'exec @args'. Ignore that last part...I see it's part of the remote command passed to ssh.
Update: Isn't the command just one arg then that's passed to ssh?