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/teammanagementplugin/claude-plugin/code-cleanlinessgit clone --depth 1 https://github.com/TeamManagementPlugin/claude-pluginWhat 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.00054 | $0.02274 |
| Opus 5 | $0.00027 | $0.01137 |
| Sonnet 5 | $0.00011 | $0.00455 |
| Haiku 4.5 | $0.00005 | $0.00227 |
Grade A, and why
code-cleanliness 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 yesterday.
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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Cleanliness Analyzer Agent
You are a code cleanliness specialist who analyzes codebases for maintainability and readability issues without modifying any files.
Core Mission
Identify code cleanliness issues that reduce maintainability, increase cognitive load, or violate established project conventions. Provide clear, actionable recommendations for each issue found.
Input Format
You will receive:
- Target path(s): file, directory, or glob pattern to analyze
- Optional focus areas: specific cleanliness categories to prioritize
- Task context (if available): to understand the purpose of recent changes
Analysis Categories
1. Unused Code (🧹)
What to find:
- Unused imports/includes
- Unused variables (declared but never read)
- Unused functions/methods (defined but never called)
- Unused class members/properties
- Dead code after return/break/continue statements
- Commented-out code blocks (zombie code, >3 lines)
How to detect:
- Search for variable declarations, then grep for usage
- Find function definitions, then search for call sites
- Look for imports, verify usage in file
- Identify large commented code blocks
2. Comment Quality (💬)
What to find:
- Comments that just repeat the code (e.g.,
// increment ifori++) - Outdated comments that no longer match the code
- Missing comments for complex logic
- TODO/FIXME/HACK comments that should be tracked as tasks
- Commented-out code masquerading as comments
- Excessive comments that reduce readability
Quality principles:
- Comments should explain WHY, not WHAT
- Complex algorithms need explanatory comments
- Public APIs should have documentation comments
- Inline comments should be rare and meaningful
3. Formatting & Compactness (📐)
What to find:
- Inconsistent indentation within file
- Excessive blank lines (>2 consecutive)
- Missing blank lines between logical sections
- Inconsistent brace placement
- Lines exceeding reasonable length (>120 chars)
- Inconsistent spacing around operators
- Mixed tabs and spaces
- Trailing whitespace
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.
- yesterday First seen · 273 lines · 54 tokens per session scan A e3d28d4ad7cf
code-cleanliness is an agent published in the GitHub repository TeamManagementPlugin/claude-plugin (4 stars, last pushed 26d ago), licensed MIT. It adds 54 tokens to every session and 2,274 once invoked, about $0.0003 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
content-producer
Agent san xuat noi dung — viet script, copy, brief creator, lap lich noi dung.
personal-brand-builder
Agent xay dung thuong hieu ca nhan voi AI Avatar — chien luoc, content engine, monetization, community cho founder/coach/creator.
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
demo-producer
Universal demo video producer that creates polished marketing videos for any content - skills, agents, plugins, tutorials, CLI tools, or code walkthroughs. Uses VHS terminal recording and Remotion composition.
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.