Ie instead of
"hey agent, use the api to get X, then do unpredictable mutation Y to it, and email it to me",
it should be;
"Scheduled task runs code to get X then place it in workspace. Task then starts agent in workspace and is prompted to do mutation Y to it. Post-flight code then sends final product."
The difference here being that the pre/post flight stuff is called deterministically, rather than called by an llm.
It ~can~ be done using standard bash utils but there just isn't a kind of standard pattern for 'move this text block via CLI tools' so the LLM and human both overlook it
Dedicated Infrastructure > automation > ad hoc scripts > non deterministic llms from a dependability perspective alone. Using an LLM to do something that prettier could have done is analogous to using a 3d printer to nail up a fence.
The tooling can remain generic and token spending focused.