worktree-clean

worktree-clean is a command for Claude Code from rohitg00/awesome-claude-code-toolkit. It costs 0 tokens per session (169 once invoked), scanned A, original, Apache-2.0.

A cleanup command for finished Git worktrees. A worktree is a separate working directory connected to the same Git repository and branch history.

In plain words
What is it for?
Use it to inspect worktrees, remove safe finished ones, prune stale references, and report what was removed or kept.
Why use it?
It helps remove unused directories and stale Git references without deleting work that is uncommitted or based on an unmerged branch.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the create-worktrees plugin — 2 commands shipped together

Good fit Use it to inspect worktrees, remove safe finished ones, prune stale references, and report what was removed or kept.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/rohitg00/awesome-claude-code-toolkit/worktree-clean
About the project

Awesome Claude Code Toolkit is a curated collection of extensions and configuration for Claude Code, including agents, skills, commands, plugins, hooks, rules, templates, MCP configurations, and companion apps. It is for Claude Code users who want ready-made workflows and integrations for different development tasks. The catalogue add-ons are selected components from this toolkit.

rohitg00/awesome-claude-code-toolkit · 2,595 stars · on GitHub

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.

Clone the repo
git clone --depth 1 https://github.com/rohitg00/awesome-claude-code-toolkit

Made for: Claude Code.

Or install create-worktrees, the plugin that ships this one along with the rest of its 2 commands.

Wrote 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.

agentmods badge for worktree-clean

README.md
[![agentmods](https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/worktree-clean.svg)](https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/worktree-clean)
Your own site
<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/worktree-clean"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/worktree-clean.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 169 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original 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.1 $0.00000 $0.00169
Opus 5 $0.00000 $0.00084
Sonnet 5 $0.00000 $0.00034
Haiku 4.5 $0.00000 $0.00017

Measured 4d ago against content hash 07d44c4839f6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

worktree-clean 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 4d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

plugins/create-worktrees/commands/worktree-clean.md · 30 lines

What it actually says

Clean up finished git worktrees by removing directories and pruning references.

Steps

  1. List all active worktrees with git worktree list.
  2. For each worktree, check its status:
  3. Identify worktrees safe to remove:
  4. For each worktree to clean:
  5. Prune stale worktree references: git worktree prune.
  6. Report what was cleaned and what was kept.

Format

Worktree Cleanup Report:
  Removed:
    - <path> (branch: <name>, reason: merged)
  Kept:

Rules

  • Never remove a worktree with uncommitted changes without user confirmation.
  • Always check if the branch is merged before deleting it.
  • Use git branch -d (not -D) to prevent deleting unmerged branches.
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. 4d ago First seen · 30 lines · 0 tokens per session scan A 07d44c4839f6

Subscribe to this mod's changes

worktree-clean is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,595 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 169 tokens. 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-09-03.