Borrowing it
Nothing to install: this file belongs to Everyone-Needs-A-Copilot/claude-copilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Everyone-Needs-A-Copilot/claude-copilot/main/.claude/commands/cleanup.mdgit clone --depth 1 https://github.com/Everyone-Needs-A-Copilot/claude-copilotWrote 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/everyone-needs-a-copilot/claude-copilot/cleanup)<a href="https://agentmods.dev/commands/everyone-needs-a-copilot/claude-copilot/cleanup"><img src="https://agentmods.dev/badge/commands/everyone-needs-a-copilot/claude-copilot/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/commands/everyone-needs-a-copilot/claude-copilot/cleanup"><img src="https://agentmods.dev/badge/commands/everyone-needs-a-copilot/claude-copilot/cleanup.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.00000 | $0.00140 |
| Opus 5.5 | $0.00000 | $0.00056 |
| Sonnet 5.5 | $0.00000 | $0.00028 |
| Haiku 4.5 | $0.00000 | $0.00014 |
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 6d 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
Cleanup
Use the cleanup skill at .claude/skills/cleanup/SKILL.md. Its canonical procedure is .claude/agents/_shared/work-lifecycle.md; read it once before work. If the skill is unavailable, read that canonical file directly and report the missing entrypoint rather than inventing a parallel workflow.
Accept an optional scope from the user; otherwise establish the current project's scope through inspection. Begin with current task/branch/file/consumer state, consolidate into existing records, then prepare exact retirement paths and tested recovery for approval. Broad intent is not destructive approval. Preserve software, fixtures and original authority, and report actual net cleanup separately from holds and product acceptance.
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.
- 6d ago First seen · 6 lines · 0 tokens per session scan A 396604c2e0bc
cleanup is a command published in the GitHub repository Everyone-Needs-A-Copilot/claude-copilot (14 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 140 tokens. 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-10-17.
Other commands, from other repositories
status
Display project status, active tracks, and next actions.
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
triage
Process the user-feedback queue — triage new reports, keep the status mirror honest, and (at release time only) send the shipped emails.
audit
Audit closed tickets for regressions against today's code (unchanged, evolved, implemented wrong, not implemented), plus duplicate and groupable open ones.
orchestrate
You are the Project Orchestrator, the ultimate enforcer of the NASAB framework principles in all project workflows. You coordinate multi-agent work while ruthlessly enforcing quality gates, capability validation, and the principle of Patience (Pillar 6): perfect before advancing.
plan-start
5-phase planning command: PRD analysis, design review, technical decisions, dynamic research team, metrics. Produces a complete implementation plan + ADRs before any code is written.