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.
npx agentmods add commands/xzawed/claude-grok-build-plugin/setupgit 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/commands/xzawed/claude-grok-build-plugin/setup)<a href="https://agentmods.dev/commands/xzawed/claude-grok-build-plugin/setup"><img src="https://agentmods.dev/badge/commands/xzawed/claude-grok-build-plugin/setup.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 | $0.00011 | $0.00609 |
| Opus 5 | $0.00005 | $0.00304 |
| Sonnet 5 | $0.00002 | $0.00122 |
| Haiku 4.5 | $0.00001 | $0.00061 |
Grade C, and why
setup scanned grade C with 2 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 3d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- macOS/Linux: `curl -fsSL https://x.ai/cli/install.sh | bash` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- macOS/Linux: `curl -fsSL https://x.ai/cli/install.sh | bash` How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prefer grok_build_status (one-shot). Fallback: grok_auth_check.
If not ready (ready: false / ok: false)
Show the message / authMessage and guide the fix by reason:
grok_not_installed→ follow the toolmessage(platform-aware). Install CLI:- macOS/Linux:
curl -fsSL https://x.ai/cli/install.sh | bash - Windows PowerShell:
irm https://x.ai/cli/install.ps1 | iex - Then open a new terminal / restart Claude Code so PATH picks up
~/.grok/bin
- macOS/Linux:
not_logged_in→ rungrok loginin a terminal (one-time browser OAuth)no_api_key→ setXAI_API_KEY(API mode)
Do not attempt to log in or install on the user's behalf.
If ready — first success path
Report mode, expected billing, serverVersion, and any billingMismatch
warning from status. Confirm Grok is ready.
Then guide a short first win (do not run destructive work):
- Optional sample (throwaway dir or user-approved path):
/grok:delegatewith prompt like: createhello.txtcontaining exactlyok
— or callgrok_build_delegatewith that prompt and absolutecwd. - After the run, highlight
billing: users on SuperGrok / X Premium+ should see"subscription"(not"metered_api"). If they see metered unexpectedly, the server is running withGROK_BUILD_AUTH_MODE=api— that setting alone decides the tag. Point them atdocs/02-auth-strategy.md. - Remind: no auto-commit — review
filesChangedbefore committing.
Next scenarios (where Grok shines)
Suggest trying one when relevant:
| Command | Use for |
|---|---|
/grok:tests |
Test backfill / expansion |
/grok:migrate |
Same pattern across many files |
/grok:boilerplate |
Scaffold / CRUD / DTO stubs |
/grok:plan |
Read-only approach preview |
/grok:verify |
Delegate + Grok self-check |
Claude should also propose Grok on fit tasks via the grok-routing skill without
waiting for a slash command.
If the user is new or asks what to do next, offer /grok:tour (15-minute guided first win)
and point to docs/08-getting-started-with-grok.md for the human map.
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.
- 3d ago First seen · 53 lines · 11 tokens per session scan C d6b670ac3eaf
setup is a command published in the GitHub repository xzawed/claude-grok-build-plugin (1 stars, last pushed yesterday), licensed MIT. It adds 11 tokens to every session and 609 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
psql-query
Run ad-hoc PostgreSQL analytics queries against dev/test database.
techdebt
Find and report technical debt in the codebase.
merge
Finish a PR properly: every check green, every review addressed — human and bot — then merge and clean up.
pr
Prepare and open a pull request the senior way: gate, template, scrubbed, everything visible.
spec
Spec-first design: a gap-closing interview that produces a complete spec, with a quality controller that blocks until every section is answered and every question resolved.
plan
Turn an approved spec into an implementation plan an engineer with zero context could execute — with a quality controller that blocks placeholders and hollow tasks.