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/jerry0022/dotclaude/setup-cleanupnpx skills add Jerry0022/dotclaude --skill setup-cleanupgit clone --depth 1 https://github.com/Jerry0022/dotclaudeWrote 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/skills/jerry0022/dotclaude/setup-cleanup)<a href="https://agentmods.dev/skills/jerry0022/dotclaude/setup-cleanup"><img src="https://agentmods.dev/badge/skills/jerry0022/dotclaude/setup-cleanup.svg" alt="Measured on agentmods" 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 | $0.00086 | $0.04668 |
| Opus 5 | $0.00043 | $0.02334 |
| Sonnet 5 | $0.00017 | $0.00934 |
| Haiku 4.5 | $0.00009 | $0.00467 |
Grade A, and why
setup-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 4d 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 — 435 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo Health Check
Analyze the repository for branch hygiene, unmerged work, and cleanup opportunities. Present results as an interactive concept page with filters and decision controls.
Step 0 — Scope selection (AskUserQuestion)
Before any git command, ask the user for scope:
Welches Repository soll analysiert werden?
(●) Aktuelles Projekt — <repo-name> (<local-path>) ← vorausgewählt
( ) Alle Projekte — aus ~/.claude/projects/ Registry
"Alle": zeigt zuerst eine Repo-Übersicht (welches Repo hat wie viel
aufzuräumen), dann Drill-down in einzelne Repos — KEIN globales
übergreifendes Bulk-Delete.
DEFAULT = current project (pre-selected). "Alle" is the explicit opt-in.
If "Alle" is selected: first generate a repo-overview page showing per-repo
counts, then let the user pick one repo for the standard single-repo flow.
Discovery: read ~/.claude/projects/ registry, dedupe (many entries are
worktree subdirs or dead paths — skip paths where git rev-parse --show-toplevel
fails or is a subdirectory of another already-listed root), fetch in parallel,
lazy. NO global cross-repo select-all.
Step 0b — Repo-mode check
Before any git command, verify this directory is a git repository:
git rev-parse --is-inside-work-tree
If this fails (exit != 0), abort:
Repo health analysiert git-Branches/Sessions — in einer Nicht-Git-Dir gibt es nichts zu pruefen. Aborting.
Do NOT proceed. End the skill.
SAFETY: Worktree Branch Protection
HARD RULE — no exceptions: Branches attached to active worktrees (Aktive Sessions) are UNTOUCHABLE. You MUST NOT:
- Delete them locally (
git branch -D) - Delete them remotely (
git push origin --delete) - Checkout/switch away from them in their worktree
- Recommend them for deletion
- Include them in any cleanup batch
These branches represent active Claude Code sessions. Deleting them breaks the worktree and causes data loss.
Detection: git worktree list --porcelain -> every line starting with
branch refs/heads/ is a protected branch. Build this set FIRST and check
it before EVERY delete operation.
What ships with it
4 files 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.
- 4d ago First seen · 435 lines · 86 tokens per session scan A 3bfbea4c3899
setup-cleanup is a skill published in the GitHub repository Jerry0022/dotclaude (5 stars, last pushed yesterday), licensed MIT. It adds 86 tokens to every session and 4,668 once invoked, about $0.0004 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-31.
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…