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/aleksandarbisevac/claude-plugins/worktreegit clone --depth 1 https://github.com/AleksandarBisevac/claude-pluginsWrote 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/aleksandarbisevac/claude-plugins/worktree)<a href="https://agentmods.dev/commands/aleksandarbisevac/claude-plugins/worktree"><img src="https://agentmods.dev/badge/commands/aleksandarbisevac/claude-plugins/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.00064 | $0.00751 |
| Opus 5 | $0.00032 | $0.00376 |
| Sonnet 5 | $0.00013 | $0.00150 |
| Haiku 4.5 | $0.00006 | $0.00075 |
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 4d 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
/audit:worktree — a git worktree for a phase (parallel runs)
Read ${CLAUDE_PLUGIN_ROOT}/reference/orchestrator.md and
${CLAUDE_PLUGIN_ROOT}/reference/manifest-conventions.md first.
Sets up an isolated git worktree so a phase can run in its own Claude session, in parallel with
other phases (best on a sharded manifest — run /audit:layout sharded first — where phase runs write
only their own shard and merge back without conflict). This only touches git worktrees/branches — it
never edits the manifest.
Resolve first (read-only): manifestPath + gitRoot from .claude/audit.config.json. If
phase.branch is already set (the phase was started), use it. Otherwise ask — do NOT compose the
name here, because meta.branch.template has cases prose gets wrong:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/manifest/resolve-branch.py" <manifestPath> --phase <phaseId>
It prints the branch name AND <parent> — the phase's resolved parent branch,
phase.parentBranch ?? meta.developmentBranch — which is what the worktree must be cut from and
merged back into. Exit 1 means the composed name is not a legal git ref; stop and report.
Worktree path: ../<repo>-<phaseId> (repo = the git-root directory's basename).
Create (default):
git -C <gitRoot> worktree add "../<repo>-<phaseId>" -b <branch> <parent>
(If <branch> already exists — the phase was started — drop -b: git -C <gitRoot> worktree add "../<repo>-<phaseId>" <branch>.)
Then print the next step for the user, e.g.:
Worktree ready at ../<repo>-<phaseId> on branch <branch>.
Open a session there and run the phase:
cd ../<repo>-<phaseId> && claude
/audit:phase <phaseId>
Remind them: run each phase in its own session/worktree; when done, merge the branch back into
<parent> (ff, else --no-ff) and remove the worktree (below). When <parent> is not the
development branch, say so — the work has not reached the development branch until that parent is
itself merged, and resolve-branch.py prints that sentence for you.
Remove (--remove):
git -C <gitRoot> worktree remove "../<repo>-<phaseId>"
(Use --force only if they confirm discarding uncommitted work; offer git branch -d <branch> after a
merged phase.)
Preflight: verify the git root is a repo and <phaseId> exists; if the target path already exists,
say so and stop (don't clobber). Never run a phase yourself — this command only prepares the worktree.
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.
- 4d ago First seen · 56 lines · 64 tokens per session scan A a034a73e39c1
worktree is a command published in the GitHub repository AleksandarBisevac/claude-plugins (4 stars, last pushed 3d ago), licensed MIT. It adds 64 tokens to every session and 751 once invoked, about $0.0003 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
post
Post the current OCR review to a GitHub PR.
show
Display a past OCR review session.
history
List past OCR review sessions.
overlay-apply
Apply NIST 800-53 overlays (FedRAMP, DoD, Privacy, etc.) to existing baselines.
sdlc
Master orchestrator for the complete 5-phase SDLC pipeline. Runs all phases sequentially with approval gates and handoffs between each phase. Organizes artifacts into handoffs/, docs/, and projects/ directories.
pillar-guidance
Deep dive guidance on DORA's 5 pillars and implementation requirements.