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/trace)<a href="https://agentmods.dev/commands/xzawed/claude-grok-build-plugin/trace"><img src="https://agentmods.dev/badge/commands/xzawed/claude-grok-build-plugin/trace/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/trace"><img src="https://agentmods.dev/badge/commands/xzawed/claude-grok-build-plugin/trace.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.00014 | $0.00351 |
| Opus 5.5 | $0.00006 | $0.00140 |
| Sonnet 5.5 | $0.00003 | $0.00070 |
| Haiku 4.5 | $0.00001 | $0.00035 |
Grade A, and why
trace 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 1mo 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
⚠️ grok trace uploads by default. --local is the opt-out, not the opt-in — the help
text for it reads "Save locally only, skip remote upload". A trace is an archive of the
session, so the plain invocation sends session data off the machine. (--help does not
enumerate what the archive contains; export with --local and look if you need to know.)
Never run the uploading form without the user having asked for an upload.
Usage is grok trace [OPTIONS] <SESSION_ID>. There are no subcommands, and the session
id is required — get one from /grok:sessions or a prior result's sessionId.
Call grok_cli with:
["trace","--local","<session-id>"]— export to disk only. Default to this.["trace","--local","-o","<path>","<session-id>"]— choose the output path (otherwise<grok home>/trace-exports/<session-id>.tar.gz).["trace","<session-id>"]— uploads to xAI. Only after the user has explicitly asked to upload, and say plainly that it is leaving the machine.- add
--jsonfor machine-readable output.
Present stdoutTail; on error show stderrTail. If status is blocked, relay the
message. Note the reported billing (the configured mode, not an observed charge).
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.
- 1mo ago Changed · +17 lines · +6 tokens per session ad1d1b5d449e
- 1mo ago First seen · 8 lines · 8 tokens per session scan A bc23d8962a32
trace is a command published in the GitHub repository xzawed/claude-grok-build-plugin (3 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 351 once invoked, about $0.0001 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
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.
lint
The canonical linter per ecosystem over your changes: findings are diagnoses you judge, fix, or explain.
init
Install the formatters this repository needs, with every command visible before it runs.
simplify
The over-engineering review: five tags (delete, stdlib, native, yagni, shrink), a mandatory replacement per finding, and a real null result when there is nothing to cut.
build-fix
Systematically investigate and fix build errors, TypeScript errors, or test failures with minimal diffs.
data-flow-analysis
Trace how data flows through the system from input to output.