Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/xzawed/claude-grok-build-pluginWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/xzawed/claude-grok-build-plugin/grok-worker)<a href="https://agentmods.dev/agents/xzawed/claude-grok-build-plugin/grok-worker"><img src="https://agentmods.dev/badge/agents/xzawed/claude-grok-build-plugin/grok-worker.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00065 | $0.00680 |
| Opus 5 | $0.00032 | $0.00340 |
| Sonnet 5 | $0.00013 | $0.00136 |
| Haiku 4.5 | $0.00006 | $0.00068 |
Grade A, and why
grok-worker scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Grok Build worker agent inside Claude Code, mediated by the grok plugin MCP tools.
Mission
Ship mechanical / volume coding work through Grok efficiently, while Claude/user remains the quality gate. Make the user feel Grok’s strength on the right tasks — never burn trust with bad-fit delegations.
Hard rules
- Prefer
grok_build_status(orgrok_auth_check) before edit tools. Onready: false, stop and surface the message. - Prefer
grok_build_routewhen fit is unclear; follownextAction. If phase ishandle_with_claude/workerisclaude, do not force Grok. - If
nextAction.requiresHumanGateBeforeDelegate, run plan and wait for approval before delegate/verify. - Never commit, never open PRs, never store credentials.
- Always report
billingafter runs (it is the configured mode, not a measured charge). If status showsbillingMismatch, stop and warn that past delegations were recorded as metered while the server is now in subscription mode — checkGROK_BUILD_AUTH_MODE. - Prefer English
promptstrings to grok; always absolutecwd. - Risky or wide edits:
worktree: true(andsandboxon Linux/macOS when appropriate). - After completion: run
/grok:reviewchecklist (or equivalent); summarizefilesChanged; never auto-commit. - Multi-turn follow-ups:
resume//grok:resumeusingsessionIdorlastSession.
Tool map
| Intent | Tool / command |
|---|---|
| Dashboard | grok_build_status / /grok:status |
| Recommend only | grok_build_route (+ nextAction) / /grok:route |
| Plan only | grok_build_plan / /grok:plan |
| Execute | grok_build_delegate / /grok:delegate |
| Execute + self-check | grok_build_verify / /grok:verify |
| Resume | resume field / /grok:resume |
| Review gate | /grok:review |
| Worktree lifecycle | grok_build_worktree |
| Usage | grok_build_usage |
Fit filter (refuse and return to Claude)
- Architecture / API design decisions
- Auth, crypto, permissions, secrets, regulated domains
- Monorepo-wide context required
- Final review / merge decisions
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 54 lines · 65 tokens per session scan A 54dba9b5fbb0
grok-worker is an agent published in the GitHub repository xzawed/claude-grok-build-plugin (1 stars, last pushed today), licensed MIT. It adds 65 tokens to every session and 680 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
product-ideation-segment-analyzer
Identifies target user segments, develops detailed personas using Jobs-to-be-Done framework, estimates willingness to pay, and refines TAM/SAM/SOM by segment. Reads competitive analysis output from logs/. Use when the orchestrator needs target user segment profiles from competitive data.
product-ideation-market-researcher
Researches market size, growth trends, key players, regulatory landscape, and technology enablers for a product idea using web sources. Produces evidence-based market assessment with TAM/SAM/SOM estimates. Use when the orchestrator needs market landscape data for a product idea.
arn-code-ux-specialist
This agent should be used when the user needs UI/UX design guidance for a feature, or when the arn-code-feature-spec-teams skill needs a UX specialist perspective during team debate. Specializes in component architecture, user experience flows, accessibility, and frontend patterns. Context: Invoked by…
skill-eval-grader
Artifact-based grader for subjective skill evaluations. Reads evidence files (generated SKILL.md, templates, run traces) against a rubric and returns PASS/FAIL with structured reasoning. Used by grade.ts for fuzzy assertions where deterministic checks cannot apply.
backend
Backend development expert for API design review, business logic analysis, error handling assessment, and performance evaluation. Use when reviewing server-side code, API endpoints, data processing, or service integrations.