cleanup

cleanup is a command for Claude Code from danielraffel/generous-corp-marketplace. It costs 10 tokens per session (769 once invoked), scanned A, original, MIT.

A command for merging changes from a separate Git worktree—a second working copy of a repository—and then removing that worktree.

In plain words
What is it for?
Merging a worktree into a branch, deleting the temporary worktree, and optionally retaining its feature branch.
Why use it?
It cleans up finished parallel development work while providing options for the target branch and branch deletion.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the worktree-manager plugin — 8 commands shipped together

Good fit Merging a worktree into a branch, deleting the temporary worktree, and optionally retaining its feature branch.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/danielraffel/generous-corp-marketplace/cleanup
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/danielraffel/generous-corp-marketplace

Made for: Claude Code.

Or install worktree-manager, the plugin that ships this one along with the rest of its 8 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 cleanup

README.md
[![agentmods](https://agentmods.dev/badge/commands/danielraffel/generous-corp-marketplace/cleanup/github.svg)](https://agentmods.dev/commands/danielraffel/generous-corp-marketplace/cleanup)
Your own site
<a href="https://agentmods.dev/commands/danielraffel/generous-corp-marketplace/cleanup"><img src="https://agentmods.dev/badge/commands/danielraffel/generous-corp-marketplace/cleanup/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for cleanup

Your own site · 80×15
<a href="https://agentmods.dev/commands/danielraffel/generous-corp-marketplace/cleanup"><img src="https://agentmods.dev/badge/commands/danielraffel/generous-corp-marketplace/cleanup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 769 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.00010 $0.00769
Opus 5 $0.00005 $0.00385
Sonnet 5 $0.00002 $0.00154
Haiku 4.5 $0.00001 $0.00077

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

Security

Grade A, and why

cleanup 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 9d 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.

plugins/worktree-manager/commands/cleanup.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Worktree Cleanup Command

Merge worktree changes to main branch and safely remove the worktree.

Usage

/worktree-manager:cleanup <worktree-path> [options]

Options

  • --merge - Auto-merge to target branch before removing
  • --target=<branch> - Branch to merge into (default: main)
  • --force - Force removal even with uncommitted changes (DANGER: loses changes)
  • --keep-branch - Don't delete feature branch after merge

Instructions for Claude

When user invokes this command:

  1. Parse arguments:

    • Extract worktree path (required)
    • Check for --merge flag → auto_merge: true
    • Extract --target=<branch>target_branch: "<branch>"
    • Check for --force flag → force: true
    • Check for --keep-branchdelete_branch: false
  2. Safety check:

    • If --force is used, warn user that uncommitted changes will be lost
    • Ask for confirmation before proceeding
  3. Call MCP tool:

    • Use mcp__worktree__worktree_cleanup
    • Pass all extracted parameters
  4. Display results:

    • Show what was done:
      • ✅ Merged (if auto_merge was true)
      • ✅ Worktree removed
      • ✅ Branch deleted (if applicable)
    • Display next steps from result
  5. Error handling:

    • If uncommitted changes and no --force:
      • Show the error
      • List the uncommitted files
      • Suggest either:
        • Commit/stash changes first
        • Use --force to discard (with warning)
    • If merge conflicts:
      • Explain the conflict
      • Provide manual resolution steps
  6. Format example:

    Cleaning up worktree: ~/worktrees/feature-name
    
    ✅ Merged feature/feature-name into main
    ✅ Worktree removed
    ✅ Branch feature/feature-name deleted
    
    Next steps:
      Push to remote: git push origin main
    

Examples

Remove without merge:

User: /worktree-manager:cleanup ~/worktrees/old-feature
Claude: [Removes worktree, keeps branch]

Merge and remove:

User: /worktree-manager:cleanup ~/worktrees/completed-feature --merge
Claude: [Merges to main, removes worktree, deletes branch]

Read the full file on GitHub · 108 lines

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. 9d ago First seen · 108 lines · 10 tokens per session scan A 36b72e55fb81

Subscribe to this mod's changes

cleanup is a command published in the GitHub repository danielraffel/generous-corp-marketplace (11 stars, last pushed 10d ago), licensed MIT. It adds 10 tokens to every session and 769 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-30.