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 skills/drn/dots/prunenpx skills add drn/dots --skill prunegit clone --depth 1 https://github.com/drn/dotsWhat 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.00031 | $0.00552 |
| Opus 5 | $0.00015 | $0.00276 |
| Sonnet 5 | $0.00006 | $0.00110 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
prune 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 2d 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.
What it actually says
Branch Cleanup
Delete merged and stale local branches safely, with preview and confirmation.
Arguments
$ARGUMENTS- Optional:--stale-days <N>to override the 30-day stale threshold,--remoteto also delete remote branches
Context
- Current branch: !
git branch --show-current - Remote: !
git remote 2>/dev/null | head -5
Instructions
Resolve the script path — use the first that exists:
~/.claude/skills/prune/scripts/prune.sh(deployed via symlink)agents/skills/prune/scripts/prune.sh(repo-relative, for development/workspaces)
Step 1: Preview branches
Run the preview command, forwarding any --stale-days argument:
bash <script-path> preview [--stale-days N]
Handle the exit code:
- Exit 0 — Present the output as a formatted table (see format below). Proceed to Step 2.
- Exit 3 — Tell the user: "All branches are current — nothing to prune." and stop.
- Exit 1 — Report the error from stderr.
Format the preview output as:
## Branch Cleanup Preview
### Merged (safe to delete)
| Branch | Last Commit | Merged Into |
|--------|------------|-------------|
| <branch> | <date> | <default> |
### Stale (no commits in N days)
| Branch | Last Commit |
|--------|------------|
| <branch> | <date> |
### Skipped
| Branch | Reason |
|--------|--------|
| <branch> | <reason> |
Step 2: Confirm and delete
Ask the user which branches to delete. Accept "all", specific branch names, or "none".
For confirmed branches, run the delete command:
bash <script-path> delete [--remote] <branch1> [branch2 ...]
Include --remote only if the user passed it in $ARGUMENTS.
Handle the exit code:
- Exit 0 — Show the output block verbatim as your final response.
- Exit 1 — Report the error from stderr.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 78 lines · 31 tokens per session scan A e3d706ccf674
prune is a skill published in the GitHub repository drn/dots (23 stars, last pushed 4d ago), licensed MIT. It adds 31 tokens to every session and 552 once invoked, about $0.0002 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…