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/thrownlemon/claude-code-plugins/removegit clone --depth 1 https://github.com/ThrownLemon/claude-code-pluginsWhat 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.00010 | $0.00660 |
| Opus 5 | $0.00005 | $0.00330 |
| Sonnet 5 | $0.00002 | $0.00132 |
| Haiku 4.5 | $0.00001 | $0.00066 |
Grade A, and why
remove 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 yesterday.
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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remove Worktree
Clean up a git worktree created by fork-terminal and unregister its worker.
What This Does
- Unregister the worker from the coordination file
- Remove the git worktree directory
- Optionally delete the branch if
--delete-branchis specified
Arguments
| Argument | Description | Default |
|---|---|---|
--path |
Worktree path or branch name | required |
--force |
Force removal with uncommitted changes | false |
--delete-branch |
Also delete the git branch | false |
Examples
# Remove by path
/fork-terminal:remove --path ../my-project-auth-refactor
# Remove by branch name
/fork-terminal:remove --path worktree/auth-refactor
# Force remove with uncommitted changes
/fork-terminal:remove --path ../my-project-tests --force
# Remove worktree and delete the branch
/fork-terminal:remove --path worktree/old-feature --delete-branch --force
Execution
Step 1: Unregister Worker
python3 ${CLAUDE_PLUGIN_ROOT}/skills/fork-terminal/tools/coordination.py unregister --path "<path>"
Step 2: Remove Worktree
python3 ${CLAUDE_PLUGIN_ROOT}/skills/fork-terminal/tools/worktree_manager.py remove "<path>" [--force] [--delete-branch]
Or combined:
# Get branch name first if needed
git worktree list --porcelain | grep -A2 "<path>"
# Remove worktree
git worktree remove [--force] "<path>"
# Delete branch if requested
git branch -D "<branch-name>"
Safety Checks
Before removing, the command will:
- Check for uncommitted changes (unless
--force) - Warn if the worktree is the current directory
- Confirm branch deletion if
--delete-branch
After Removal
The worktree directory and its contents will be deleted. If you have uncommitted changes you want to keep:
- Commit them first in the worktree
- Or use
git stashbefore removing - Or copy files manually before removal
Troubleshooting
"Worktree is locked"
git worktree unlock <path>
/fork-terminal:remove --path <path>
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.
- yesterday First seen · 107 lines · 10 tokens per session scan A b9cf7e72c2b0
remove is a command published in the GitHub repository ThrownLemon/claude-code-plugins (2 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 660 once invoked, about $0.0001 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-31.
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.