Work
Quota alarm triage: cut routine freq, prune memory, write bans
Quota alarms. Buying more credits feels easier than cleaning what each bot carries every turn.
What hurt
Mai Yang (@MaiYangAI) maps Cursor’s agent-harness token cuts (shorter prompts, selective tools, cache, compressed reads) onto Grok Bot quota care: lower routine frequency, prune expired memory, write clear bans — more useful than opening a new quota. When the meter screams, first check how much useless context each bot carries per turn. Tip only — no invented prompt. Not affiliated with xAI.
What to install or create
Alarm → inventory per-bot baggage → cut routines → prune memory → write bans. New quota last.
Bots
Token / quota officer (optional)
Lists heavy routines and fat memory when the meter alarms.
Plugins
None on day one. Follow the first-run steps.
Files
Optional: one-page ban list each bot must read (never send / never buy / never …).
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/MaiYangAI/status/2102905702549533157.
- 2When quota alarms, list what each bot carries every turn (skills, memory, tool dumps).
- 3Lower routine frequency first. Pause chatty bot-to-bot loops.
- 4Prune expired memory. Write clear bans so the bot stops retrying forbidden paths.
- 5Only then consider more quota — after the harness is lean.
Approval fence
Do not buy credits or change billing without your yes. Deleting memory is irreversible — confirm first.
What to tweak
Steal the triage order. Clean harness before you buy more meter.
Source
Mai Yang @MaiYangAI · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
Pro pack
Want the full setup, not just the idea?
Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.