agents-close-gitworktree

A command for closing a Git worktree, which is a separate working directory linked to a repository branch, after work is finished or abandoned.

In plain words
What is it for?
Use it to identify the current worktree, record whether the work was merged or abandoned, and add closeout notes to the tracking registry.
Why use it?
It keeps the project’s worktree tracking record accurate and can optionally remove the closed worktree.

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/gpt-cmdr/ras-commander/agents-close-gitworktree
Clone the repo
git clone --depth 1 https://github.com/gpt-cmdr/ras-commander

Made for: Claude Code.

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 920 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00920
Opus 5 $0.00000 $0.00460
Sonnet 5 $0.00000 $0.00184
Haiku 4.5 $0.00000 $0.00092

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

Security

Grade A, and why

agents-close-gitworktree 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 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.

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.

.claude/commands/agents-close-gitworktree.md · 135 lines

How it starts

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

You are closing out a git worktree after completing (or abandoning) work. This command updates the tracking registry and optionally removes the worktree.

Your Task

1. Identify the Worktree to Close

Options:

  • Current worktree: Detect from git branch --show-current
  • User-specified: Ask if multiple options exist
  • From registry: Read agent_tasks/git_worktree_status.md and let user choose
# Get current branch
CURRENT_BRANCH=$(git branch --show-current)

# List all worktrees
git worktree list

2. Determine Closeout Status

Ask the user or infer from context:

  • merged: Work was completed and merged to main/target branch
  • abandoned: Work was stopped before completion (document why)

If merged, ask for:

  • PR number or link (if applicable)
  • Brief summary of what was accomplished

If abandoned, ask for:

  • Reason for abandonment
  • Whether work should be picked up later

3. Update Tracking Registry

Edit agent_tasks/git_worktree_status.md:

  1. Find the entry for this branch in "Active Worktrees"
  2. Add closeout information:
    - **Closed**: {YYYY-MM-DD HH:MM}
    - **Status**: merged | abandoned
    - **Closeout Notes**: {summary, PR link, or reason for abandonment}
    
  3. Move the entire entry to "Closed Worktrees" section

4. Handle Git Cleanup

Ask user preference:

Option A: Full Cleanup (recommended for merged work)

# Return to main repo
cd {MAIN_REPO_PATH}

# Remove worktree
git worktree remove {WORKTREE_PATH}

# Delete local branch (if merged)
git branch -d {BRANCH_NAME}

# Delete remote branch (if pushed)
git push origin --delete {BRANCH_NAME}

# Prune stale references
git worktree prune

Option B: Keep Worktree (for reference or future work)

  • Only update registry
  • Leave worktree and branch intact

Option C: Partial Cleanup

  • Remove worktree but keep branch
  • Useful if work might resume from different location

5. Report Completion

Worktree Closed Successfully

Branch: {branch-name}
Status: {merged|abandoned}
{Closeout Notes}

Registry updated: agent_tasks/git_worktree_status.md

{If cleanup performed:}
- Worktree removed: {yes/no}
- Local branch deleted: {yes/no}
- Remote branch deleted: {yes/no}

Read the full file on GitHub · 135 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. 3d ago First seen · 135 lines · 0 tokens per session scan A 7ae755b0b154

Subscribe to this mod's changes

agents-close-gitworktree is a command published in the GitHub repository gpt-cmdr/ras-commander (78 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 920 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-08-30.