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 commands/superclaude-org/superclaude_framework/cleanupgit clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_FrameworkWrote 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/superclaude-org/superclaude_framework/cleanup)<a href="https://agentmods.dev/commands/superclaude-org/superclaude_framework/cleanup"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_framework/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.00016 | $0.00707 |
| Opus 5 | $0.00008 | $0.00353 |
| Sonnet 5 | $0.00003 | $0.00141 |
| Haiku 4.5 | $0.00002 | $0.00071 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- cleanup — 91% identical, 31 lines differ
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sc:cleanup - Code and Project Cleanup
Triggers
- Code maintenance and technical debt reduction requests
- Dead code removal and import optimization needs
- Project structure improvement and organization requirements
- Codebase hygiene and quality improvement initiatives
Usage
/sc:cleanup [target] [--type code|imports|files|all] [--safe|--aggressive] [--interactive]
Behavioral Flow
- Analyze: Assess cleanup opportunities and safety considerations across target scope
- Plan: Choose cleanup approach and activate relevant personas for domain expertise
- Execute: Apply systematic cleanup with intelligent dead code detection and removal
- Validate: Ensure no functionality loss through testing and safety verification
- Report: Generate cleanup summary with recommendations for ongoing maintenance
Key behaviors:
- Multi-persona coordination (architect, quality, security) based on cleanup type
- Framework-specific cleanup patterns via Context7 MCP integration
- Systematic analysis via Sequential MCP for complex cleanup operations
- Safety-first approach with backup and rollback capabilities
MCP Integration
- Sequential MCP: Auto-activated for complex multi-step cleanup analysis and planning
- Context7 MCP: Framework-specific cleanup patterns and best practices
- Persona Coordination: Architect (structure), Quality (debt), Security (credentials)
Tool Coordination
- Read/Grep/Glob: Code analysis and pattern detection for cleanup opportunities
- Edit/MultiEdit: Safe code modification and structure optimization
- TodoWrite: Progress tracking for complex multi-file cleanup operations
- Task: Delegation for large-scale cleanup workflows requiring systematic coordination
Key Patterns
- Dead Code Detection: Usage analysis → safe removal with dependency validation
- Import Optimization: Dependency analysis → unused import removal and organization
- Structure Cleanup: Architectural analysis → file organization and modular improvements
- Safety Validation: Pre/during/post checks → preserve functionality throughout cleanup
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 · 93 lines · 16 tokens per session scan A 9cf3d63465ff
cleanup is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Framework (23,866 stars, last pushed 13d ago), licensed MIT. It adds 16 tokens to every session and 707 once invoked, about $0.0001 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 commands, from other repositories
pr-address
Address PR review comments on current branch.
enforce_standards
CRITICAL: Before running the code standards enforcer, we must prepare the stack properly and abort if there are merge conflicts.
OPSX: Verify
Verify implementation matches change artifacts before archiving.
OPSX: Continue
Continue working on a change - create the next artifact (Experimental).
OPSX: Sync
Sync delta specs from a change to main specs.
context
项目上下文管理：初始化 .context 目录、记录决策日志、压缩归档、查看历史.