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/lexfrei/ccc/cleanup-allnpx skills add lexfrei/ccc --skill cleanup-allgit clone --depth 1 https://github.com/lexfrei/cccWrote 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/lexfrei/ccc/cleanup-all)<a href="https://agentmods.dev/skills/lexfrei/ccc/cleanup-all"><img src="https://agentmods.dev/badge/skills/lexfrei/ccc/cleanup-all.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.00094 | $0.00646 |
| Opus 5 | $0.00047 | $0.00323 |
| Sonnet 5 | $0.00019 | $0.00129 |
| Haiku 4.5 | $0.00009 | $0.00065 |
Grade A, and why
cleanup-all 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 5d 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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrate the cleanup skills end to end and report total disk reclaimed.
Each stage keeps its own report → confirm → execute gate, and each gathers its own options through interactive questions — this orchestrator passes no flags. The user approves (or skips) each stage independently.
Step 0: Resolve shared inputs (never hardcode paths)
- Scan root for the filesystem stages (worktrees, forks): resolve from
$ARGUMENTS, else infer the hosting root by walking up from the current directory and ask the user to confirm or correct it, else ask outright. Do not assume a default. Resolve this once and reuse it for both filesystem stages. - Which stages to run: ask the user (interactive, multi-select) which of the five stages to include — worktrees, forks, docker, go, brew. Default to all available ones.
Announce the plan: which stages will run, in what order, with the resolved scan root.
Stages (run the selected ones in order)
Run each by following the corresponding sibling skill in this plugin. Each sibling asks its own scope questions (volumes, modcache, delete-remote, etc.) — do not try to pre-answer them here. Carry the running total of reclaimed space across stages.
- worktrees →
worktree-sweepon the resolved scan root (all-repos scope). Remove safe worktrees; triage dirty ones. - forks →
stale-forkson the resolved scan root. Remove dead/reclonable local clones; the sibling asks per-fork about deleting the GitHub fork. - docker →
docker-prune. The sibling asks which scopes (images/cache, volumes, non-default buildx builders, VM disk trim on VM-backed daemons). - go →
go-cache. The sibling asks whether to include the module cache. - brew →
brew-cleanup. The sibling asks which scopes (cleanup, autoremove, full cache scrub).
If a stage's prerequisite is absent (no Docker daemon, no go, no brew, no repositories under the root), report that and continue to the next stage instead of failing the pipeline.
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.
- 5d ago First seen · 34 lines · 94 tokens per session scan A 7023a0450381
cleanup-all is a skill published in the GitHub repository lexfrei/ccc (9 stars, last pushed 2d ago), licensed BSD-3-Clause. It adds 94 tokens to every session and 646 once invoked, about $0.0005 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…