Engineering
A 5-minute routine costs ~12× an hourly one
Same bot, same prompt — the clock is what burns the allowance.
What hurt
Ruslan (@RDV1113) full course: one routine every 5 minutes wakes ~8,640 times/month (~$400 at API rates vs ~$33 hourly). On a subscription you see allowance burn, not a line item. His rules: event triggers over polling, slowest schedule the job can live with, cheap "did anything change?" gate before expensive work, never let a night routine wait for approval, keep your own run log (product keeps ~20). Not affiliated with xAI.
What to install or create
Audit routine intervals. Slow what can wait; gate fast checks; log runs yourself.
Bots
No new bot. Follow the first-run steps.
Plugins
None on day one. Follow the first-run steps.
Files
routine-run-log.md. Your log of routine fires and whether anything changed.
Routines
None on the first run. Watch one manual pass first.
The prompt
This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.
First run
- 1Read https://x.com/RDV1113/status/2109581928907034894 (credit @RDV1113).
- 2List every routine and its interval.
- 3For each: switch to event trigger if possible, else the slowest schedule that still works.
- 4Add a cheap change-detect step before expensive work on any remaining fast routine.
- 5Start a personal run log; never leave overnight routines blocked on your approval.
Approval fence
Do not enable new sub-hourly routines without your yes.
What to tweak
Steal the cadence math. Frequency is a cost knob, not a virtue.
Source
Ruslan Dranovskiy @RDV1113 · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
Pro pack
Routine cost control: stop running out of usage by Wednesday
A one-hour audit, a quiet Usage officer and a fix playbook (cadence, silence, event triggers, fresh chats, scripts over clicks) that cut waste without losing the jobs your bots do.