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-cleanup.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-cleanup)<a href="https://agentmods.dev/commands/wbern/agent-instructions/worktree-cleanup"><img src="https://agentmods.dev/badge/commands/wbern/agent-instructions/worktree-cleanup/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-cleanup"><img src="https://agentmods.dev/badge/commands/wbern/agent-instructions/worktree-cleanup.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.00021 | $0.03323 |
| Opus 5.5 | $0.00008 | $0.01329 |
| Sonnet 5.5 | $0.00004 | $0.00665 |
| Haiku 4.5 | $0.00002 | $0.00332 |
Grade B, and why
worktree-cleanup scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
<read_worktree_settings>{worktree_path}/.claude/settings.local.json</read_worktree_settings> How it starts
The opening of the file, as written. The whole thing — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Worktree Cleanup
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).
Clean up merged worktrees by finding the oldest merged branch, consolidating settings, and removing stale worktrees.
User arguments:
Worktree-cleanup: $ARGUMENTS
End of user arguments
<current_state>
Current branch: git branch --show-current
Current worktrees: git worktree list
</current_state>
<execution_steps> <step_0> Detect git hosting provider and available tools
<detect_provider> <check_remote_url>git remote get-url origin</check_remote_url> <identify_host> - github.com → GitHub - gitlab.com → GitLab - bitbucket.org → Bitbucket - Other → Ask user </identify_host> </detect_provider> <check_available_tools> <list_mcp_servers>Check which git-hosting MCP servers are available (github, gitlab, etc.)</list_mcp_servers> <check_cli>Check if gh/glab CLI is available as fallback</check_cli> </check_available_tools> <select_tool> <if_single_mcp>If only one relevant MCP available, confirm with user</if_single_mcp> <if_multiple>Let user choose which tool to use</if_multiple> <if_told_earlier>If user specified tool earlier in conversation, use that without asking again</if_told_earlier> <store_as>$GIT_HOST_TOOL (e.g., "github_mcp", "gitlab_mcp", "gh_cli")</store_as> </select_tool>
Detect git hosting provider and select appropriate tool for PR verification </step_0>
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 · 271 lines · 21 tokens per session scan B d897ede42f48
worktree-cleanup is a command published in the GitHub repository wbern/agent-instructions (168 stars, last pushed 5mo ago), licensed MIT. It adds 21 tokens to every session and 3,323 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.