Use cases / Ops
Grok Bot for spend watcher
How to run spend watcher with Grok Bot: which Bot owns it, what it reads and produces, the cadence, the approval gate, and the specific risk to watch.
Short answerOps Bot, daily 07:00: reads usage page, produces spend-log.csv line; alerts at 60/85%. Gate: none (never pauses anything).
| Function | Ops |
| Tools | Cursor dashboard, Slack |
| Owning Bot | Ops Bot |
| Cadence | Daily 07:00 |
| Reads (bounded) | Usage page |
| Produces | spend-log.csv line; alerts at 60/85% |
| Approval gate | None (never pauses anything) |
How it runs
The Ops Bot owns this as part of its theme. On its cadence it reads usage page, produces spend-log.csv line; alerts at 60/85%, and stops. It writes one heartbeat line to the ops log so a missed run shows up in the morning message.
The risk to watch
Reads the dashboard, not the app meter.
Setup
- Bot identity with a seat in: Cursor dashboard, Slack. See own accounts.
- Test supervised three times, then schedule.
- Four-part routine shape: routines best practices.
Part of the founder chief of staff playbook.
Verified 28 Aug 2026 · Facts about Grok Bot change during beta. See changelog.