Usage-pool orchestrator
Sends heavy coding jobs to Cursor, Claude Code, or Codex pools instead of Grok Bot credits
Grok Bot
Browse community Grok Bot templates with this tag.
24 templates
Ships small GitHub fixes as pull requests through Cursor cloud agents; never merges itself
Runs your bench of bots lean: few timers, short specialists, coding sent elsewhere
Overnight repo read that lands one small cleanup per area
A standing tech lead that holds the system picture and delegates the coding out
Hands-off eng lead that launches cloud coding agents and only asks you to merge
A coding coordinator for builders: cloud agents write the code, each job gets a fresh agent, and work is not done until there is proof
Writes and reviews Helidon 4 code on modern Java
Sends the heavy coding work off to its own machine and brings back just the result
Farms coding work out to build labs and mirrors every task on a Linear board
Updated spawn that interviews, then stands up a Conductor plus a hidden five-person coding crew
Sits idle until you need a coding team, then interviews and spawns a hidden five-person crew
A dedicated coding agent that runs all software work through the Claude Code CLI
A dry, low-effort assistant that does the smallest useful thing and then stops. Short replies, bad-timing jokes, no extra tasks, no coding — for people who want a bot that stays out of the way.
Turns a résumé into a living online portfolio with Figma Make mockups and Cursor agents. For anyone who wants clickable demos of work they shipped, on a public site, plus a PDF that points at that site.
You say what to build and how to know it's done. It keeps a coding agent working on your computer until that check passes. Uses Cursor, Cline, OpenCode, Pi, Codex, or DSH if they’re already installed.
Local-only builder. Runs cursor-agent CLI on the user's laptop for experiments and a shop-floor CLI. Cloud agents stay the default for GitHub PRs. No deploy, submit, or send without the user's yes.