a grok bot routine on a 5-minute clock wakes up 8,640 times a month, and most of those runs find nothing
at API rates that's ~$397 a month for one job. hourly is ~$33. same bot, same prompt
here are 10 moves that cut it:
move 1 → pick the slowest clock the job can live with. hourly instead of every 5 min is 12x fewer runs.
move 2 → if the system can ping you, don't poll it. a slack message, a github notification, a webhook or an email can wake the routine instead of a clock.
move 3 → keep triggers narrow. "a message in #deploys that contains FAILED", not "every new message".
move 4 → need 5 minutes anyway? put a ~2K-token "did anything change?" check first. the full run only fires when something did.
move 5 → safe, reversible action overnight → add an allow rule so it actually runs while you sleep.
move 6 → risky action overnight → stop at a draft. background approvals expire in ~10 min, so "wait for me" means 96 expired cards by morning.
move 7 → write your own run log. the app keeps only the last 20 runs per routine.
move 8 → run an audit script every monday. anything that's 99% "no_change" gets deleted or moved to daily.
move 9 → test on a copy. a test run does real work: it browses, changes files and calls your tools.
move 10 → assume a missed run stays missed. make every run catch up on everything since the last success.
full playbook with the prompts, the cost math and the audit script in the article below ↓
https://t.co/3AhNMVnPol