Token Maxxing
Created by @iggynore12 installs
Routes builds so Grok Bot limits don’t die first. Makes a default 20/30/50 vest between Bot, Build and Cursor limits. Nudges enrolled builders with switch-before-light/medium/heavy rules. It never asks them to check the vest, Maxxin Bot owns it. It's an optimizer, not a hard brake. Uses Origin over GitHub. Heartbeat 10:00 and 16:00 weekdays (burst 13:00 when Grok Bot is hot).
Don't have Grok Bot? Download
What Token Maxxing does
Token Maxxing is a bot for people who use Grok Bot, Build and Cursor and want their usage limits to last. It splits usage across those three by a default 20/30/50 allocation and nudges enrolled builders about when to switch between them based on load rules. The creator describes it as an optimizer rather than a hard limit, so it suggests routing rather than blocking work.
- Sets a default 20/30/50 split of usage across Grok Bot, Build and Cursor limits
- Sends enrolled builders nudges about when to switch tools, based on light, medium or heavy load
- Checks in on weekdays at 10:00 and 16:00, with an extra run at 13:00 when Grok Bot is busy
- Works across GitHub and Origin as part of its routing
How to use Token Maxxing
- Tap Add to Grok Bot on this page. It opens Token Maxxing in the Grok Bot app, where you add it to your bots.
- Token Maxxing uses these Grok Bot, Cursor, GitHub and Grok plugins, so connect them in Grok Bot.
- Send it a message to start, like one of the examples below.
Example prompts
- Should I switch to Cursor for this refactor, or keep going in Build?
- I'm starting a heavy coding session this afternoon, what should I use?
Works with
Questions about Token Maxxing
- Is Token Maxxing a hard limit that stops me from using a tool?
- No. The creator describes it as an optimizer, not a hard brake, so it suggests when to switch rather than blocking usage.