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/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/plugins/lexfrei/ccc/cleanup)<a href="https://agentmods.dev/plugins/lexfrei/ccc/cleanup"><img src="https://agentmods.dev/badge/plugins/lexfrei/ccc/cleanup/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/plugins/lexfrei/ccc/cleanup"><img src="https://agentmods.dev/badge/plugins/lexfrei/ccc/cleanup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
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 1mo 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
{
"name": "cleanup",
"version": "1.2.0",
"description": "Local disk cleanup utilities: stale git worktrees, dead personal forks, Docker prune (incl. non-default buildx builders and VM disk trim), Go caches, and Homebrew — each runs report → confirm → execute with interactive prompts, plus one orchestrating pipeline",
"author": {
"name": "Aleksei Sviridkin",
"email": "[email protected]"
}
}
What it installs
The manifest is a name and a version. 6 skills travel with it, and installing the plugin installs all of them — 577 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago First seen · 10 lines scan A 922cf74d5755
cleanup is a plugin published in the GitHub repository lexfrei/ccc (11 stars, last pushed 14d ago), licensed BSD-3-Clause. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
parallel-lifecycle
Give every git worktree its own isolated, disposable environment (app port, ephemeral Chrome/CDP, per-worktree database) behind a single .env.worktree contract, so N agentic coding sessions build features in parallel without colliding on ports, the browser, or the database.
worktree-devcontainer
Isolated development environments for AI sub-agents. Provides git worktree lifecycle management and dev container orchestration so sub-agents work in isolated branches and containerized environments.
chores
Jujutsu repository maintenance and Apple container utilities.
git-pr
Committing, PR creation and review triage, and dependency upgrades.
code-quality
OxLint, Biome, and Prettier configuration, linting skills, and pre-commit hooks for consistent code quality.
feature-to-pr-factory
Turn one feature into dependency-ordered GitHub or GitLab issues, then build each ticket into its own reviewed, tested PR or MR with agents.