Work
Tip only: use a Grok Bot, not Grok web, for a separate usage pool
Grok on the web can eat the same usage pie as Grok Build. A Bot can sit on a separate pool.
What hurt
Keith (@KorpioProd) tip for maximizing @build usage: do not use @grok directly on the web — it currently eats the same pie. Create a Grok @bot instead (he uses the researcher template) and you get a completely separate usage pool. Tip only — no invented prompt. Not affiliated with xAI.
What to install or create
Skip Grok web for heavy work. Spin a Bot from a template. Route research/coding asks there.
Bots
Researcher (or your pick)
Owns work that would otherwise hit the shared web/Build pie.
Plugins
None on day one. Follow the first-run steps.
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/KorpioProd/status/2102517195020308815 and check your Grok / Build meters.
- 2In Grok web, create a Grok Bot (researcher template or another you trust).
- 3Send the next heavy ask to that Bot instead of the Grok web chat.
- 4Compare meters after one session. Keep using the Bot path if the split holds.
Approval fence
Confirm meters in your account before relying on this. Product quotas can change.
What to tweak
Steal Bot-not-web for a separate meter. Check your own meters — pools can change.
Source
Keith Wingo @KorpioProd · 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.