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.
git clone --depth 1 https://github.com/danielraffel/generous-corp-marketplaceWrote 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.
[](https://agentmods.dev/commands/danielraffel/generous-corp-marketplace/prune)<a href="https://agentmods.dev/commands/danielraffel/generous-corp-marketplace/prune"><img src="https://agentmods.dev/badge/commands/danielraffel/generous-corp-marketplace/prune/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.
<a href="https://agentmods.dev/commands/danielraffel/generous-corp-marketplace/prune"><img src="https://agentmods.dev/badge/commands/danielraffel/generous-corp-marketplace/prune.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00008 | $0.00511 |
| Opus 5 | $0.00004 | $0.00255 |
| Sonnet 5 | $0.00002 | $0.00102 |
| Haiku 4.5 | $0.00001 | $0.00051 |
Grade C, and why
prune 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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- You manually deleted a worktree directory (rm -rf) How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Worktree Prune Command
Remove administrative data for worktrees that have been manually deleted.
Usage
/worktree-manager:prune
Instructions for Claude
When user invokes this command:
-
No arguments needed:
- This command operates on all orphaned worktrees automatically
-
Call MCP tool:
- Use
mcp__worktree__worktree_prune - No parameters needed
- Use
-
Display results:
- If orphans found:
- ✅ Pruned N orphaned worktree(s)
- List each pruned path
- Explain what was cleaned up
- If no orphans:
- ✅ No orphaned worktrees found
- All worktree references are valid
- If orphans found:
-
Error handling:
- Permission errors → explain and suggest solutions
- Git errors → suggest checking git installation
Examples
With orphans:
User: /worktree-manager:prune
Claude: ✅ Pruned 2 orphaned worktree(s):
- ~/worktrees/old-feature
- ~/worktrees/experiment
These directories were manually deleted but still had
git references. Those references have been cleaned up.
No orphans:
User: /worktree-manager:prune
Claude: ✅ No orphaned worktrees found
All worktree references are valid
When to Use
Use this command when:
- You manually deleted a worktree directory (rm -rf)
- Worktrees still show in /worktree-manager:list but don't exist
- You get errors about missing worktree paths
- After bulk cleanup of old worktree directories
- Before checking worktree status to clean up stale references
What It Does
Prune removes git's administrative references for worktrees whose directories no longer exist. This cleans up:
.git/worktrees/<name>directories in the main repo- Stale entries in git's worktree list
- Broken references that cause git warnings
Safe Operation
This is a safe operation:
- Only removes references to non-existent directories
- Does not delete any actual worktree directories
- Does not modify any existing worktrees
- Can be run anytime without risk
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.
- 9d ago First seen · 85 lines · 8 tokens per session scan C 943f22a1f569
prune is a command published in the GitHub repository danielraffel/generous-corp-marketplace (11 stars, last pushed 10d ago), licensed MIT. It adds 8 tokens to every session and 511 once invoked, about $0.0000 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.
Other commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
handoff
Export a Waybill Bundle by default, or import one when requested.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.