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/commands/xzawed/claude-grok-build-plugin/inspect)<a href="https://agentmods.dev/commands/xzawed/claude-grok-build-plugin/inspect"><img src="https://agentmods.dev/badge/commands/xzawed/claude-grok-build-plugin/inspect/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/xzawed/claude-grok-build-plugin/inspect"><img src="https://agentmods.dev/badge/commands/xzawed/claude-grok-build-plugin/inspect.svg" alt="Reviewed on agentmods" width="80" 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.00009 | $0.00389 |
| Opus 5.5 | $0.00004 | $0.00156 |
| Sonnet 5.5 | $0.00002 | $0.00078 |
| Haiku 4.5 | $0.00001 | $0.00039 |
Grade A, and why
inspect 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 23d 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_cli with args: ["inspect", "--json"] (append any extra flags the user gave).
⚠️ This output is large — measured ~81 KB on an ordinary machine, against a 4,000-character
default. For inspect (and help, --help, -h) the tool keeps the FIRST characters, not the
last, and reports stdoutKept: "head". When the result carries stdoutTruncated: true,
stdoutTail is the FIRST 4,000 characters of a much longer document (stdoutTotalChars gives the
real size) and will not parse as JSON. Do not present it as the parsed config, and do not guess
at the parts you cannot see.
- Truncated — say so, quote
stdoutTotalChars, and summarise only what is legible in the kept head. If the user needs the whole document, offer to call again withmax_chars: 100000(the ceiling; ~81 KB fits, at that token cost). For a specific section, offergrok_cliwithargs: ["inspect"](the plain form is smaller), or have them rungrok inspect --json > inspect.jsonin their terminal and read the file. - Not truncated —
stdoutTailis the whole document; parse and present it. (IfstdoutCutShortistrue, the output may stop before its end — the run hit its time cap, or reading stopped while something grok started still held it: treat it as incomplete, like a truncated one.)
On error show stderrTail. If status is blocked, relay the message.
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.
- 23d ago Changed · +4 lines 3a4513e77351
- 1mo ago Changed · +12 lines e49514a414eb
- 1mo ago First seen · 8 lines · 9 tokens per session scan A 73d8fdd65416
inspect is a command published in the GitHub repository xzawed/claude-grok-build-plugin (3 stars, last pushed today), licensed MIT. It adds 9 tokens to every session and 389 once invoked, about $0.0000 per session on Opus 5.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
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.
debug
Systematic debugging: root cause before any fix, one hypothesis at a time, and a three-strikes rule that questions the architecture instead of stacking patches.
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.