Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add bengous/claude-code-plugins/plugin install git-worktreeWrote 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/bengous/claude-code-plugins/worktree-setup)<a href="https://agentmods.dev/commands/bengous/claude-code-plugins/worktree-setup"><img src="https://agentmods.dev/badge/commands/bengous/claude-code-plugins/worktree-setup/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/bengous/claude-code-plugins/worktree-setup"><img src="https://agentmods.dev/badge/commands/bengous/claude-code-plugins/worktree-setup.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.00012 | $0.00305 |
| Opus 5.5 | $0.00005 | $0.00122 |
| Sonnet 5.5 | $0.00002 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
worktree-setup 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 24d 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
Git Worktree Setup
You are installing the git worktree convention enforcement system.
What This Installs
git-wthelper - Creates worktrees at../<repo>.wt/<name>/with stack support for multi-agent orchestrationgit-worktree-hook- Claude Code PreToolUse hook that blocks incorrect paths- CLAUDE.md update - Adds convention to global instructions
- Settings hook - Registers the PreToolUse hook
Your Task
Step 1: Check Current State
Check what's already installed:
"${CLAUDE_PLUGIN_ROOT}/scripts/worktree-setup" check
Step 2: Run Installation
When the check reports every component installed, say so and stop. Otherwise run:
"${CLAUDE_PLUGIN_ROOT}/scripts/worktree-setup" install
The script does every file operation; edit none of the files it manages by hand.
Step 3: Report Results
Relay what the install printed: each component and where it went, the usage lines, and any error verbatim. Add that the PreToolUse hook now blocks worktrees created outside ../<repo>.wt/<name>/.
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.
- 24d ago Changed · -26 lines 80ab55a97f9b
- 1mo ago Changed · -1 lines eaa1d5d4a6e0
- 1mo ago First seen · 69 lines · 12 tokens per session scan A dcb4d110792c
worktree-setup is a command published in the GitHub repository bengous/claude-code-plugins (5 stars, last pushed today), licensed MIT. It adds 12 tokens to every session and 305 once invoked, about $0.0000 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-09-03.
Other commands, from other repositories
context
A project-context command that manages a .context directory containing decision notes, session logs, and history. It helps keep a record of why changes were made across Git branches and commits.
clean-branches
A Git command for finding and safely removing local or remote branches that are already merged or have not been updated for a chosen number of days. Git branches are separate lines of code history used for features, fixes, or experiments.
rollback
An interactive Git command for moving a branch back to an earlier commit, tag, or saved reference. It supports reset, which changes branch history, and revert, which adds new commits that undo earlier ones.
land
Resolve and squash merge one named, currently authorized pull request.
resolve-pr
Resolve PR review feedback — fetch unresolved threads, triage, dispatch resolver agents, reply + resolve via GraphQL.
wrap
The session-scoped landing step after ship: flips board rows, merges green PRs, checks deploys, tidies worktrees, prints the skim-first report. Use when the operator says to wrap up, close out the session, or land the work: 'wrap up', 'close out', 'session wrap', 'land it', 'tổng kết session', 'wrap lại đi'. Also the…