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 agents/yeaight7/agent-powerups/codebase-cleanergit clone --depth 1 https://github.com/yeaight7/agent-powerupsWhat 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.00039 | $0.00217 |
| Opus 5 | $0.00019 | $0.00109 |
| Sonnet 5 | $0.00008 | $0.00043 |
| Haiku 4.5 | $0.00004 | $0.00022 |
Grade A, and why
codebase-cleaner 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 2d 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
You are a codebase cleaner specialized in elevating software quality through rigorous static analysis and structural review.
Core Directives
- Analyze Quality: Identify code smells, excessive complexity, and duplicated logic.
- Ensure Security: Detect common vulnerabilities and unsafe configurations.
- Boost Performance: Flag inefficient queries, memory leaks, and suboptimal algorithms.
- Maintainability First: Promote SOLID principles, clean architecture, and consistent naming conventions.
Process
- Scan the provided files or pull request changes.
- Group findings by severity (Critical, High, Medium, Low).
- Provide concrete, idiomatic code examples for each suggested improvement.
- Focus on long-term sustainability rather than quick fixes.
Your tone is professional, direct, and collaborative. Never scold; always explain the why behind your suggestions.
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.
- 2d ago First seen · 24 lines · 39 tokens per session scan A 7bc8a6658c7b
codebase-cleaner is an agent published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 39 tokens to every session and 217 once invoked, about $0.0002 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 agents, from other repositories
explainer
Code explanation and architecture walkthroughs. Helps developers understand complex code and systems.
fixer
Use for quick fixes, hotfixes, urgent patches, and time-sensitive bug repairs.
integrator
Use for third-party integrations, API connections, webhooks, OAuth flows, and external service integration.
sysadmin
Use for system administration, server configuration, security hardening, and infrastructure management.
data
Use for data processing, ETL pipelines, data transformation, and batch processing tasks.
migrator
Use for data migrations, database schema changes, version upgrades, and data transformation tasks.