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/helmedeiros/clean-code-skills/clean-code-auditgit clone --depth 1 https://github.com/helmedeiros/clean-code-skillsWhat 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.00057 | $0.00736 |
| Opus 5 | $0.00028 | $0.00368 |
| Sonnet 5 | $0.00011 | $0.00147 |
| Haiku 4.5 | $0.00006 | $0.00074 |
Grade A, and why
clean-code-audit 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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clean Code Audit
Perform a comprehensive code quality audit on the current project. Evaluate the codebase against all 20 clean code skills and produce a structured report.
Audit Process
Step 1: Scan the Codebase
Identify the primary language(s), framework(s), and project structure. Focus on source files, excluding vendored dependencies and generated code.
Step 2: TDD Assessment
- Check for test files and test coverage patterns.
- Evaluate whether tests follow the Arrange-Act-Assert pattern.
- Look for test-first indicators (test files matching source files, comprehensive edge case coverage).
- Flag untested public methods or classes.
Step 3: Refactoring Opportunities
- Identify long methods that should be extracted (more than 20 lines of logic).
- Flag poorly named variables, methods, or classes.
- Detect complex conditionals (nested if/else, switch statements with shared logic) that could use polymorphism.
Step 4: SOLID Compliance
- SRP: Flag classes with multiple reasons to change (mixed concerns).
- OCP: Look for modification-heavy code that should use extension points.
- LSP: Check inheritance hierarchies for contract violations.
- ISP: Find large interfaces that force clients to depend on unused methods.
- DIP: Identify high-level modules directly depending on low-level implementations.
Step 5: OOP Review
- Check for data classes with no behavior (anemic domain models).
- Flag exposed internal state (public fields, getter/setter pairs without invariants).
- Identify deep inheritance hierarchies that should use composition.
Step 6: Functional Programming Opportunities
- Spot impure functions with hidden side effects.
- Identify loops that could be replaced with map/filter/reduce.
- Find null-based error handling that could use Result/Either/Option patterns.
Step 7: Architecture Assessment
- Evaluate dependency direction (do domain modules depend on infrastructure?).
- Check for port/adapter separation at system boundaries.
- Flag domain logic mixed with I/O, serialization, or framework code.
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 · 104 lines · 57 tokens per session scan A 21112d1c918d
clean-code-audit is a command published in the GitHub repository helmedeiros/clean-code-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 57 tokens to every session and 736 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 commands, from other repositories
upgrade
Upgrade the skillshare CLI binary and/or the built-in skillshare skill.
rust-features
Get Rust version changelog and new features.
diff
Compare two SKILL.md files section-by-section. Parses frontmatter and body sections independently, showing exactly what changed.
writing:review
Exhaustive parallel editorial review of written content.
add-skill
Scaffold a new skill with validation, plugin generation, and README update.
new-skill
Scaffold a new skill directory following this repo's spec.