例行成本控制：别再周三就把额度用光

The payoff

Stop running out of Grok Bot usage by Wednesday without losing the jobs your bots do. This pack gives you a one-hour audit, a quiet Usage officer bot that reviews your fleet every week, and a set of rules (cadence, silence, event triggers, fresh chats, scripts over clicks) that fix the usual leaks.

Why it matters, in numbers other people have published: one routine every 5 minutes wakes about 8,640 times a month, which @RDV1113 estimated at roughly $400 at API rates versus about $33 for the same job run hourly. Fan Grok Bot Radar found one of their routines firing 672 times a week and rereading the whole chat each time, and cut it to hourly with the same signal (@GrokBotRadar). Krista Letz, who sells Grok Bot, cut her Gmail scan from every 15–30 minutes to twice a day (as reported by @GrokBotRadar). Those are their numbers. Run the audit and you'll have yours.

What it saves: usage you already pay for, and the on-demand spend or plan upgrade you might otherwise buy to cover leaks.

Who this is for

• Anyone with three or more routines, or any routine that runs more than a few times a day.
• People who hit their weekly limit and don't know which bot did it.
• Anyone about to buy a bigger plan. Do this first.

How it works

1. Inventory: a copyable list of every routine, its cadence and runs per week (@justinfredette: you can't cut what you haven't listed).
2. Audit: find the top three drains with a paste-in prompt.
3. Fix, one dial at a time: slower cadence, silence on no change, event triggers instead of polling, a thin lead bot, fresh chats, scripts instead of repeated browser clicks.
4. Guard: a Usage officer reviews the fleet every Friday and stays quiet when nothing needs fixing.

A taste: the audit prompt

Quoted from Fan Grok Bot Radar (@GrokBotRadar). Paste it into the bot that owns your routines:

Audit your own usage for me. List every routine you own. For each one, tell me:
1. How often it runs
2. How many runs that is per week
3. Whether it posts a message even when nothing changed
4. Whether this is also the Bot I chat with most
Then tell me which one is costing me the most and how to slow it down
without breaking the job.

Where this comes from

• Cadence math and "never let a night routine wait for approval": Ruslan (@RDV1113). Free use-case: /use-cases/five-minute-routine-costs-12x.
• How often × how much it rereads, plus the full checklist: Fan Grok Bot Radar (@GrokBotRadar), /use-cases/stop-week-usage-in-a-day.
• Six habits (connectors before the browser, max two retries): @xrDLP. Ten token burners: Warren Redlich (@WR4NYGov).
• Thin lead bot: @Ken_LinkWell. Scripts instead of clicks: Sam Sokolin (@SamSokolin). Token Officer job: @dataguybobby.
• Cheap script on the computer, webhook only on change: 铁柱AGI (@cgnot996). Enabled isn't fired: @workinsiders.