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/statusgit 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/status)<a href="https://agentmods.dev/commands/xzawed/claude-grok-build-plugin/status"><img src="https://agentmods.dev/badge/commands/xzawed/claude-grok-build-plugin/status.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.00237 |
| Opus 5 | $0.00005 | $0.00118 |
| Sonnet 5 | $0.00002 | $0.00047 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
status 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 5d 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.
What it actually says
Call grok_build_status (preferred one-shot). If unavailable, call grok_auth_check
then grok_build_usage and combine.
Present a short dashboard:
- Ready?
ready/authMessage(andreasonif not ready → guide/grok:setup) - Mode & expected billing (
mode,billing) +serverVersion - Billing mismatch? if
billingMismatch: true, warn prominently — the server is in subscription mode but past delegations were recorded as metered, soGROK_BUILD_AUTH_MODEwasapifor some of them - Usage:
usageHeadline, success/subscription rates when present - Last session:
lastSession.sessionIdif any → mention/grok:resume - Next: follow
nextSteps(do not invent IDs or skip billing)
Read-only — no edits, no commit. For post-edit review use /grok:review.
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.
- 5d ago First seen · 20 lines · 11 tokens per session scan A 9029ac368950
status is a command published in the GitHub repository xzawed/claude-grok-build-plugin (1 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 237 once invoked, about $0.0001 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 commands, from other repositories
ask
Query multiple AI agents (Gemini, OpenAI, Grok, Perplexity, Kimi, any model OpenRouter routes to, and a local ollama model) for diverse perspectives on architecture decisions, technology choices, debugging dead-ends, and security tradeoffs. Use this whenever the user names the council directly, whatever the topic …
result
Fetch, list, or cancel background council jobs started with --async.
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.
backlog
The project layer: milestones, epics, and user stories with refusing controllers — spec-seeded, sprint-ready.