remove-worktree

A command for removing one Git worktree, its directory, the linked Git reference, and its branch.

In plain words
What is it for?
Use it to delete a specific worktree and its associated Git data.
Why use it?
It cleans up a separate working copy after the related task is finished. This avoids leaving unused directories and Git references behind.

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/mdmatk/tormentnexus/remove-worktree
Clone the repo
git clone --depth 1 https://github.com/MDMAtk/TormentNexus

Made for: Claude Code.

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,115 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.00013 $0.01115
Opus 5 $0.00006 $0.00558
Sonnet 5 $0.00003 $0.00223
Haiku 4.5 $0.00001 $0.00112

Measured 2d ago against content hash 30827642947b, 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 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.

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"
third_party/rtk/.claude/commands/tech/remove-worktree.md · 156 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

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. 2d ago First seen · 156 lines · 13 tokens per session scan C 30827642947b

Subscribe to this mod's changes

remove-worktree is a command published in the GitHub repository MDMAtk/TormentNexus (11 stars, last pushed 1mo ago), with no licence file. It adds 13 tokens to every session and 1,115 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.