Grok Bot routines burn budget: check first, run on change
The author warns that Grok Bot's 50 routines per bot on a shared 5-minute clock burn budget, and proposes a read-only pre-check so full runs only happen on change, with a six-role prompt.
SIX GROK BOTS, ONE F*CKING TIMER, AND IT WAS EATING THE WHOLE BUDGET Grok Bot lets one bot own up to 50 routines, and almost every setup gives each of them the same 5-minute clock. The idea: every wake is a fresh run you pay for, so the only question is whether that wake had a reason to happen. A tiny read-only check answers that before the model does anything, and the full run only starts when the answer is yes. You just tell your lead bot this: split the night shift, check first here's the split: → the lead picks the slowest clock each routine can live with, or deletes it for an event → every wake reads one hash, count or date, answers in one word and stops, 2K tokens, $0.0043 → only a change hands the job to a full run, 20K in and 1K out, about $0.046 → every run writes one csv line, because the app only keeps the last 20 three things quietly burn your bill: → a 5-minute clock on a job that changes twice a day, that's 8,640 wakes and about $397 a month → a night step that waits for you, unattended approvals expire in about 10 minutes and nothing runs → testing on live data, test runs are real runs Check first. Run on change. Draft at night. the full crew > timekeeper picks the clock, or swaps it for a webhook, Slack, GitHub or email event > hasher runs the read-only check before every wake turns into work > runner does the full run only when the hash moved > nightwatch ends every 3 a.m. step at a draft or an Allow automatically rule > scribe writes one line per run to routines/log/[name].csv > the lead reads the logs every Monday and slows down anything that is 99% no_change paste the crew and this prompt into Grok Bot ↓ "Set up my routines around this crew: 1. List every routine with its schedule, trigger and monthly cost. 2. Replace each clock with an event where one exists, and pick the slowest schedule for the rest. 3. Put a read-only hash check in front of every routine and start a full run only on change. 4. End every night step at a draft, and add Ask first rules for sending, paying and deleting. 5. Log every run to routines/log/[name].csv and audit them every Monday at 09:00. Show me old and new monthly cost side by side. Nothing changes until I say go." ↳ http://docs.x.ai/grok-bot/settings-and-notifications run it for one night. at breakfast you get the drafts, the log and a bill that went from $397 to $45.
This post quotes another post: x.com/gippp69/status/2109235458383216811