remove-worktree

A command for removing one specific Git worktree, its directory, its Git reference, and its branch. A worktree is an additional checkout of a repository.

In plain words
What is it for?
Use it after completing work in a named worktree when that checkout and its branch are no longer needed.
Why use it?
It cleans up all parts of a finished worktree so leftover directories or Git references do not remain.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/florianbruniaux/claude-code-ultimate-guide/remove-worktree
Clone the repo
git clone --depth 1 https://github.com/FlorianBruniaux/claude-code-ultimate-guide

Made for: Claude Code.

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 948 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00015 $0.00948
Opus 5 $0.00008 $0.00474
Sonnet 5 $0.00003 $0.00190
Haiku 4.5 $0.00002 $0.00095

Measured 3d ago against content hash 69f80559fdf6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

remove-worktree scanned grade C 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 3d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf "$WORKTREE_FULL_PATH" 2>/dev/null || true
.claude/commands/remove-worktree.md · 131 lines

The source is not reproduced here

Licensed CC-BY-SA-4.0

The repository is licensed CC-BY-SA-4.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

Changes

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.

  1. 3d ago First seen · 131 lines · 15 tokens per session scan C 69f80559fdf6

Subscribe to this mod's changes

remove-worktree is a command published in the GitHub repository FlorianBruniaux/claude-code-ultimate-guide (5,863 stars, last pushed yesterday), licensed CC-BY-SA-4.0. It adds 15 tokens to every session and 948 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.