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/worktreegit 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/worktree)<a href="https://agentmods.dev/commands/xzawed/claude-grok-build-plugin/worktree"><img src="https://agentmods.dev/badge/commands/xzawed/claude-grok-build-plugin/worktree.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.00015 | $0.00550 |
| Opus 5 | $0.00008 | $0.00275 |
| Sonnet 5 | $0.00003 | $0.00110 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
worktree 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
Use the MCP tool grok_build_worktree (preferred over raw grok_cli worktree for
wrapper-managed trees under ~/.grok-build/worktrees).
- list —
action: "list",cwd= absolute repo path. Show paths/branches. - diff —
action: "diff",cwd,worktree_pathfrom a prior delegate withworktree: true. - apply —
action: "apply"to copy uncommitted worktree diff intocwdviagit apply. Never commit. Tell the user to review the working tree. If apply fails, do not force. - remove —
action: "remove"only for paths under~/.grok-build/worktrees(tool enforces). It also deletes the companiongrok/<name>branch withgit branch -d, so isolated runs stop accumulating branches.-d(not-D) means git refuses when the branch holds unmerged commits; the tool then reportsbranchDeleted: falseand leaves it for the user. - prune —
action: "prune",cwd, optionalmax_age_days(default 7). Dry run unlessapply: true. Show thecandidateslist first and let the user decide.createdDaysAgois the age of the directory itself, i.e. when it was created. Editing a file inside it does not refresh that, so do not present it as "unused for N days".- A candidate with
dirty: trueholds uncommitted work;applyskips those and reports them inskippedDirty. To remove one anyway, useaction: "remove"on it explicitly, afteraction: "diff". owneris the repo that registered the tree. The base dir is global, so trees from other projects appear here too; prune removes each through its own owner. Trees git no longer knows are reported inremovedOrphan.
Always use absolute paths. On error, show the tool message. Remind: no auto-commit.
Note: grok's own grok worktree gc does not see these trees — it tracks a different set.
Use this tool, not that one, for anything under ~/.grok-build/worktrees.
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 First seen · 31 lines · 15 tokens per session scan A 762c405d7473
worktree is a command published in the GitHub repository xzawed/claude-grok-build-plugin (1 stars, last pushed 10d ago), licensed MIT. It adds 15 tokens to every session and 550 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
psql-query
Run ad-hoc PostgreSQL analytics queries against dev/test database.
techdebt
Find and report technical debt in the codebase.
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.
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.