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/resume)<a href="https://agentmods.dev/commands/xzawed/claude-grok-build-plugin/resume"><img src="https://agentmods.dev/badge/commands/xzawed/claude-grok-build-plugin/resume.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.1 | $0.00011 | $0.00427 |
| Opus 5 | $0.00005 | $0.00214 |
| Sonnet 5 | $0.00002 | $0.00085 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
resume 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 2d 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
Continue Grok work in the same session instead of starting cold.
Steps
- Call
grok_auth_check. Ifok: false, stop and showmessage. - Call
grok_build_usagewith the project absolutecwd(and a smalllimitif desired). - Read
lastSession.sessionId(preferred). If missing, scanrecentfor the newest entry that hassessionId. - If still no session id:
- Tell the user there is no resumable session in history yet.
- Suggest a fresh
/grok:delegate(or usesessionIdfrom a prior tool result if they still have it in chat). - Stop without inventing an id.
- Call
grok_build_delegatewith:prompt= the user's follow-up taskcwd= absolute project path (preferlastSession.cwdwhen it matches the project)resume= that sessionId (do not also setcontinue)
- 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, and the newsessionIdif returned. - Do not commit — user/Claude review the diff first.
Notes
- Resume is for multi-turn Grok context, not a substitute for Claude's plan/review.
- Prefer low-risk follow-ups (fix-ups, more tests, same-scope edits). For a new risky
direction, use
/grok:planor a fresh delegate withworktree: true. - Never pass per-call auth mode; billing stays on the server
GROK_BUILD_AUTH_MODE.
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.
- 2d ago Changed · +3 lines 37266e44bbf2
- 7d ago First seen · 31 lines · 11 tokens per session scan A ca0ca343d9e1
resume 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 427 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.
docs
The documentation report: references, diagrams, drift, API docs, badges, README structure, links, Pages.
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.