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/boilerplate)<a href="https://agentmods.dev/commands/xzawed/claude-grok-build-plugin/boilerplate"><img src="https://agentmods.dev/badge/commands/xzawed/claude-grok-build-plugin/boilerplate/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/boilerplate"><img src="https://agentmods.dev/badge/commands/xzawed/claude-grok-build-plugin/boilerplate.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.00010 | $0.00238 |
| Opus 5 | $0.00005 | $0.00119 |
| Sonnet 5 | $0.00002 | $0.00048 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
boilerplate 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 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.
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
Preset: use Grok for boilerplate / scaffolding (CRUD, DTOs, handlers, thin modules).
- Call
grok_auth_check. Ifok: false, showmessageand stop (guide/grok:setup). - Build an English
promptwith:- What to create (names, paths, stack conventions in this repo)
- Patterns to mirror (existing file as reference if any)
- What not to invent (no extra features, no drive-by refactors)
- Call
grok_build_delegatewith absolutecwd. Useworktree: trueif the scaffold spans many new files in a shared package. - If
statusis notcompleted(auth_error,timeout, orgrok_error), show the returnedmessageand stop — do not report the run as done;filesChangedmay still list partial edits. Otherwise showsummary,filesChanged,billing. Review diffs; do not commit.
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 Changed · +3 lines 79285ab8432d
- 8d ago First seen · 14 lines · 10 tokens per session scan A d5e6a5b2aa86
boilerplate is a command published in the GitHub repository xzawed/claude-grok-build-plugin (1 stars, last pushed 2d ago), licensed MIT. It adds 10 tokens to every session and 238 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
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.
copilot-leak
Copilot's auto-review escapes: find them since the last look, sanitise them, and turn each one into a lesson.
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.
docs
The documentation report: references, diagrams, drift, API docs, badges, README structure, links, Pages.