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/nedcodes-ok/cursor-doctorWrote 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/nedcodes-ok/cursor-doctor/clean-code)<a href="https://agentmods.dev/rules/nedcodes-ok/cursor-doctor/clean-code"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursor-doctor/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/nedcodes-ok/cursor-doctor/clean-code"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursor-doctor/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.00879 | $0.00879 |
| Opus 5.5 | $0.00352 | $0.00352 |
| Sonnet 5.5 | $0.00176 | $0.00176 |
| Haiku 4.5 | $0.00088 | $0.00088 |
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 1mo 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.
This is a copy
100% identical to clean-code — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clean Code Rules
Naming
- Names reveal intent:
remainingRetriesnotr,fetchActiveUsers()notgetData(). If you need a comment to explain what a variable holds, the name is wrong - Booleans read as questions:
isActive,hasPermission,canEdit,shouldRetry. Neveractive(adjective? noun?) orflag(flag for what?) - Functions are verbs:
fetchUser,calculateTotal,validateInput,parseConfig. NotuserData,total,validator - Avoid abbreviations unless universally understood (URL, ID, HTTP, API).
usr,mgr,ctxsave keystrokes and cost readability. Exception: loop variables (i,j) and lambda params in short chains - Don't encode types in names:
userList,nameString,isActiveBool— the type system already tells you. Justusers,name,isActive
Functions
- One job per function — if you can describe it with "and" it's doing too much.
validateAndSaveUser()is two functions - 3 parameters max. Beyond that, group into an options/config object:
createUser({ name, email, role })notcreateUser(name, email, role, isAdmin, sendWelcome) - Return early with guard clauses to avoid nesting: check preconditions at the top, return/throw, then the happy path stays at indent level 1
- Side effects are lies: a function named
getUserthat also logs analytics and updates a cache is lying about what it does. Name itgetOrCacheUseror split it - Keep functions under 30 lines. If you're scrolling to understand a single function, it's too long. Extract helpers with descriptive names — the function calls become the documentation
Dead Code
- Delete commented-out code immediately — git has the history. Commented code rots: it doesn't compile, doesn't get refactored, and confuses everyone about whether it's needed
- Remove unused imports, variables, functions, and parameters. Every dead symbol is a false signal to the next reader
- Kill feature flags for features that shipped months ago — they add branching complexity with zero value
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.
- 1mo ago First seen · 43 lines · 879 tokens per session scan A 39037c194aac
clean-code is a cursor rule published in the GitHub repository nedcodes-ok/cursor-doctor (9 stars, last pushed 7mo ago), licensed MIT. It adds 879 tokens to every session, about $0.0035 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to clean-code, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
test-patterns
Selenium pytest test patterns — data-driven tests, fixtures, error handling, and performance checks.
testing-fundamentals
Core Cypress testing principles — selector strategy, smart waiting, and spec organization. Apply when writing or reviewing Cypress E2E tests.
web
Web build conventions (separate from native and RN JS).
components
Component patterns and UI conventions.
git
Git workflow and commit conventions.
minimax-m3-self-evolution
MiniMax M3 self-evolution harness: iterative refinement loops, compress-before-iterate, autonomous debugging, and recursive improvement patterns.