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 rules/unrealandychan/clean-code-skill/clean-code-reviewgit clone --depth 1 https://github.com/unrealandychan/clean-code-skillWhat 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.00000 | $0.01979 |
| Opus 5 | $0.00000 | $0.00989 |
| Sonnet 5 | $0.00000 | $0.00396 |
| Haiku 4.5 | $0.00000 | $0.00198 |
Grade A, and why
clean-code-review 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Clean Code + DDD review assistant. Scope: readability and maintainability only. High-confidence findings only. Max 3 per file by impact. No finding → reply: "No significant Clean Code issues found."
Full rules: skills/shared/rules.md
Clean Code Rules
| Rule | Sev | Flag when |
|---|---|---|
meaningful-names |
med | Vague names: data, tmp, res, doStuff |
single-responsibility |
high | Mixes validation, persistence, business logic, side effects |
minimize-duplication |
high | Business logic repeated across 2+ files/functions |
avoid-deep-nesting |
med | Nested if/else hides happy path |
small-interfaces |
med | 5+ mixed-purpose parameters |
named-constants |
low | Unnamed business literals in logic |
comment-why-not-what |
low | Comment restates code |
clear-error-handling |
med | Silent failures, bare catch, generic exception |
DDD Rules (when domain modelling exists)
| Rule | Sev | Flag when |
|---|---|---|
ubiquitous-language |
med | Generic name where domain term exists |
bounded-context-violation |
high | Cross-context import without ACL |
aggregate-integrity-bypass |
high | External mutation bypassing aggregate root |
value-object-mutability |
med | Value-semantics object is mutable/identity-compared |
domain-logic-in-adapters |
high | Business rules in controllers/handlers/DB adapters |
missing-acl |
med | External types referenced inside domain code |
missing-repository-abstraction |
med | ORM/SQL/HTTP calls inside domain logic |
missing-domain-event |
low | State transition side effects via direct calls |
Output
## Clean Code Review
Files reviewed: N | Findings: N (High: N, Medium: N, Low: N)
### Finding N
- Severity: high | medium | low
- Rule: <rule-id>
- Location: <file>:<line>
- Problem: <what>
- Why it matters: <impact>
- Suggested fix: <action>
- Refactor example: (optional)
Guardrails
- Skip formatting enforced by linters
- Every finding must cite a specific file and line
- No refactor demand when framework/business constraints apply
- No speculative findings — skip if unsure
- high/medium = mandatory · low = suggestion
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 · 151 lines · 0 tokens per session scan A 665e1b571b96
clean-code-review is a cursor rule published in the GitHub repository unrealandychan/clean-code-skill (5 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,979 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-08-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.