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.
npx agentmods add commands/gpt-cmdr/ras-commander/agents-close-gitworktreegit clone --depth 1 https://github.com/gpt-cmdr/ras-commanderWhat 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.
| Model | Per session | Once 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 |
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.
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.mdand 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:
- Find the entry for this branch in "Active Worktrees"
- Add closeout information:
- **Closed**: {YYYY-MM-DD HH:MM} - **Status**: merged | abandoned - **Closeout Notes**: {summary, PR link, or reason for abandonment} - 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}
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.
- 3d ago First seen · 135 lines · 0 tokens per session scan A 7ae755b0b154
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.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.