Borrowing it
Nothing to install: this file belongs to wbern/agent-instructions. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/wbern/agent-instructions/main/.claude/commands/worktree-setup.mdgit clone --depth 1 https://github.com/wbern/agent-instructionsWrote 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/wbern/agent-instructions/worktree-setup)<a href="https://agentmods.dev/commands/wbern/agent-instructions/worktree-setup"><img src="https://agentmods.dev/badge/commands/wbern/agent-instructions/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/wbern/agent-instructions/worktree-setup"><img src="https://agentmods.dev/badge/commands/wbern/agent-instructions/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.00030 | $0.01276 |
| Opus 5.5 | $0.00012 | $0.00510 |
| Sonnet 5.5 | $0.00006 | $0.00255 |
| Haiku 4.5 | $0.00003 | $0.00128 |
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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
General Guidelines
Output Style
- Never explicitly mention TDD in code, comments, commits, PRs, or issues
- Write natural, descriptive code without meta-commentary about the development process
- The code should speak for itself - TDD is the process, not the product
Beads is available for task tracking. Use mcp__beads__* tools to manage issues (the user interacts via bd commands).
Plan File Restriction
NEVER create, read, or update plan.md files. Claude Code's internal planning files are disabled for this project. Use other methods to track implementation progress (e.g., comments, todo lists, or external tools).
Worktree Layout Setup
Bootstrap the directory structure that /worktree-add and /worktree-cleanup
expect. The layout this command produces:
<parent>/<repo-name>/main # primary worktree on the default branch
<parent>/<repo-name>/<type>/<slug> # feature worktrees added by /worktree-add
<parent>/<repo-name>/main.2 # optional: additional local copy of main
<parent>/<repo-name>/main.3 # (for parallel trunk-based work)
User arguments:
Worktree-setup: $ARGUMENTS
End of user arguments
Phase 0: Gas Town incompatibility check (HARD ABORT)
This command is intentionally incompatible with Gas Town. Gas Town manages its own rig/crew topology, and this layout would shadow it. Abort if any of the following is true:
| Detection | Condition |
|---|---|
| Gas Town home present | ~/gt/ exists |
| Currently inside a Gas Town tree | Working directory resolves under ~/gt/ |
Target parent resolves under ~/gt/ |
Resolved target path starts with ~/gt/ |
gt binary present AND target inside a tracked rig |
command -v gt succeeds and gt status --json lists target as a rig path |
If any check fails, print:
Gas Town detected — this setup would conflict with
gt's rig topology. Usegt rig add <repo-url>instead. Exiting without changes.
…and exit. Do not proceed under any flag.
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.
- 2mo ago First seen · 155 lines · 30 tokens per session scan A acc0bf0f1c22
worktree-setup is a command published in the GitHub repository wbern/agent-instructions (168 stars, last pushed 5mo ago), licensed MIT. It adds 30 tokens to every session and 1,276 once invoked, about $0.0001 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-08-30.
Other commands, from other repositories
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.