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 gopherguides/gopher-ai/plugin install go-workflowWrote 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/gopherguides/gopher-ai/remove-worktree)<a href="https://agentmods.dev/commands/gopherguides/gopher-ai/remove-worktree"><img src="https://agentmods.dev/badge/commands/gopherguides/gopher-ai/remove-worktree/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/gopherguides/gopher-ai/remove-worktree"><img src="https://agentmods.dev/badge/commands/gopherguides/gopher-ai/remove-worktree.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.00009 | $0.01604 |
| Opus 5.5 | $0.00004 | $0.00642 |
| Sonnet 5.5 | $0.00002 | $0.00321 |
| Haiku 4.5 | $0.00001 | $0.00160 |
Grade A, and why
remove-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 1mo 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remove Worktree
This command interactively removes a single git worktree. Unlike /prune-worktree which auto-removes all safe worktrees, this command lets you select a specific worktree and handles cases where the issue isn't closed or branch isn't merged.
Usage: /remove-worktree (no arguments - interactive selection)
Clear Worktree State
Clear any active worktree state so the pre-tool-use hook doesn't block cleanup commands:
!"${CLAUDE_PLUGIN_ROOT}/scripts/worktree-state.sh" clear 2>/dev/null || true
Context
- Repository name: !
basename \git rev-parse --show-toplevel 2>/dev/null` 2>/dev/null || echo "unknown"` - Default branch: !
git remote show origin 2>/dev/null | grep 'HEAD branch' | sed 's/.*: //' || echo "main" - All worktrees: !
git worktree list 2>&1 || echo "No worktrees found" - Issue worktrees: !
git worktree list 2>/dev/null | grep -E "issue-[0-9]+" || echo "No issue worktrees found"
Steps
CRITICAL: When executing bash commands below, use backticks (`) for command substitution, NOT $(). Claude Code has a bug that mangles $() syntax into broken commands. Copy the commands exactly as written.
1. Get Repository Info
!REPO_NAME=basename \git rev-parse --show-toplevel``
!echo "Repository: $REPO_NAME"
2. List All Issue Worktrees
!echo "Scanning for issue worktrees..." !git worktree list
Filter for worktrees matching the {REPO_NAME}-issue-* pattern and display them as a numbered list.
!git worktree list | grep -E "/${REPO_NAME}-issue-[0-9]+" | cat -n
If no issue worktrees are found, inform the user and stop: "No issue worktrees found matching the pattern '{REPO_NAME}-issue-*'"
3. Ask User to Select Worktree
Use AskUserQuestion to ask: "Which worktree would you like to remove? Enter the number from the list above, or the full path."
Store the selected worktree path and extract:
WORKTREE_PATH: The full path to the worktreeBRANCH_NAME: The branch associated with the worktreeISSUE_NUM: The issue number extracted from the directory 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.
- 1mo ago First seen · 171 lines · 9 tokens per session scan A ebdb84497f1c
remove-worktree is a command published in the GitHub repository gopherguides/gopher-ai (21 stars, last pushed yesterday), licensed MIT. It adds 9 tokens to every session and 1,604 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-08-30.
Other commands, from other repositories
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
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.
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.
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.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…