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/gopherguides/gopher-ai/remove-worktreegit clone --depth 1 https://github.com/gopherguides/gopher-aiWhat 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.00009 | $0.01604 |
| Opus 5 | $0.00005 | $0.00802 |
| Sonnet 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 2d 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.
- 2d 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 2d ago), licensed MIT. It adds 9 tokens to every session and 1,604 once invoked, about $0.0000 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.