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.
git clone --depth 1 https://github.com/btseee/clean-code-skillsWrote 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/rules/btseee/clean-code-skills/clean-code)<a href="https://agentmods.dev/rules/btseee/clean-code-skills/clean-code"><img src="https://agentmods.dev/badge/rules/btseee/clean-code-skills/clean-code/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/btseee/clean-code-skills/clean-code"><img src="https://agentmods.dev/badge/rules/btseee/clean-code-skills/clean-code.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00965 | $0.00965 |
| Opus 5.5 | $0.00386 | $0.00386 |
| Sonnet 5.5 | $0.00193 | $0.00193 |
| Haiku 4.5 | $0.00097 | $0.00097 |
Grade A, and why
clean-code 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 21d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clean Code
Use these rules for every coding task in Cursor.
Clean Code Rules (clean-code-skills)
Non-negotiable for all code work.
Read the skill before non-trivial work. First existing path wins: .claude/skills/clean-code/SKILL.md, .agents/skills/clean-code/SKILL.md, .github/skills/clean-code/SKILL.md, skills/clean-code/SKILL.md. Then your stack's packs, named by the skill's scripts/detect_stack.py or references/framework-map.md.
Load project context first. If present: .clean/context.json, .clean/architecture.md, .clean/decisions.md, .clean/ledger.md, .clean/structure.md rows for your area; then project instruction files. Recorded decisions are settled. Project instructions outrank this block.
Work Loop
- Frame: behavior change, design-relevant assumptions, smallest scope, success check.
- Read first: nearby code, naming, tests, error style, framework idioms; search for existing implementations.
- Place: owning unit; which side of which boundary.
- Edit surgically: smallest diff, targeted edits (no whole-file regeneration), nothing unrelated; remove what your change orphaned.
- Verify: narrowest meaningful check, broader as risk demands.
- Review the diff against these rules, missing tests included.
Layers
- Undeclared layers (
.clean/architecture.md): follow framework pack's idiomatic structure. - Declared: Dependency Rule strict; source dependencies point inward, to higher-level policy; nothing inner names anything outer (class, function, variable, annotation, data format).
- Business rules highest; database, web, UI, framework are details behind policy-owned interfaces.
- SQL stays in data access; rows, ORM types, framework request/response objects never travel inward. Never derive business objects from framework base classes or annotate them; dependency-injection wiring in
main. - Component graph acyclic; no speculative boundary, layer, or service.
File And Code Placement
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.
- 21d ago Changed · -3 lines · -355 tokens per session 3424819e8652
- 1mo ago Changed · +13 tokens per session 13381268a2da
- 1mo ago First seen · 73 lines · 1,307 tokens per session scan A 3ad86c73ed92
clean-code is a cursor rule published in the GitHub repository btseee/clean-code-skills (14 stars, last pushed 22d ago), licensed MIT. It adds 965 tokens to every session, about $0.0039 per session on Opus 5.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 cursor rules, from other repositories
backend-rules
A Cursor rule named backend-rules covering backend development, project structure, technology choices, runtime environment, and main process. Cursor is a coding editor with rules that guide how an agent works in a project.
website-shower
Read-only Website Shower cleanup audit.
refactorer
Refactorer agent.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.