clean-code-hygiene

clean-code-hygiene is a cursor rule for Cursor from GoranErhartic/cursor-development-rules. It costs 24 tokens per session (794 once invoked), scanned A, original, MIT.

Guidelines for keeping code clean and focused. They cover removing dead code, naming fixed values, writing useful comments, failing early, and avoiding premature optimization.

In plain words
What is it for?
Use them when cleaning up code, reviewing changes, choosing comments, or deciding whether an optimization is justified.
Why use it?
They prevent clutter and hidden assumptions that make code harder to maintain or debug.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/goranerhartic/cursor-development-rules/clean-code-hygiene
Clone the repo
git clone --depth 1 https://github.com/GoranErhartic/cursor-development-rules

Made for: Cursor.

Wrote 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.

agentmods badge for clean-code-hygiene

README.md
[![agentmods](https://agentmods.dev/badge/rules/goranerhartic/cursor-development-rules/clean-code-hygiene.svg)](https://agentmods.dev/rules/goranerhartic/cursor-development-rules/clean-code-hygiene)
Your own site
<a href="https://agentmods.dev/rules/goranerhartic/cursor-development-rules/clean-code-hygiene"><img src="https://agentmods.dev/badge/rules/goranerhartic/cursor-development-rules/clean-code-hygiene.svg" alt="Measured on agentmods" height="20"></a>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 794 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00024 $0.00794
Opus 5 $0.00012 $0.00397
Sonnet 5 $0.00005 $0.00159
Haiku 4.5 $0.00002 $0.00079

Measured yesterday against content hash 673893b12ffa, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

clean-code-hygiene 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.

.cursor/rules/patterns/clean-code-hygiene.mdc · 109 lines

How it starts

The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Clean Code: Code Hygiene and Pragmatic Rules

Delete Dead Code

Never comment out code "for later." Version control preserves history. Dead code creates confusion about what's active.

// BAD - Commented code clutters and confuses
function calculateTotal(items) {
    // const subtotal = items.reduce((a, b) => a + b.price, 0)
    // const tax = subtotal * 0.08
    // return subtotal + tax
    return items.reduce((sum, item) => sum + item.price * 1.08, 0)
}

// GOOD - Clean, only active code
function calculateTotal(items) {
    return items.reduce((sum, item) => sum + item.price * 1.08, 0)
}

No Magic Numbers or Strings

Extract literals into named constants that explain their purpose.

// BAD - What do these numbers mean?
if (retryCount > 3) { }
await sleep(86400000)
if (status === 'A') { }

// GOOD - Self-documenting constants
const MAX_RETRY_ATTEMPTS = 3
const ONE_DAY_MS = 24 * 60 * 60 * 1000
const STATUS_ACTIVE = 'A'

if (retryCount > MAX_RETRY_ATTEMPTS) { }
await sleep(ONE_DAY_MS)
if (status === STATUS_ACTIVE) { }

Comment Discipline

Default stance: minimize comments. Well-named functions, variables, and clear structure should make code self-documenting.

Do NOT:

  • Add inline comments that narrate what the next line does ("Get the user", "Check if valid")
  • Add JSDoc/JavaDoc that merely restate the method signature
  • Add class or module header comments that repeat the class name

When comments ARE valuable:

  • Business rules, regulatory or compliance reasons
  • Non-obvious workarounds or "why not the obvious approach"
  • Links to external references (tickets, RFCs, specs)
// GOOD - Comment explains why (business context)
// Users inactive for 90+ days lose premium status per policy update 2024-03
if (daysSinceLastLogin > 90) {
    revokePremiumStatus(user)
}

Fail Fast

Validate inputs at system boundaries. Throw errors early rather than propagating bad state.

// BAD - Error surfaces far from cause
function processOrder(order) {
    // ... 50 lines of processing ...
    sendEmail(order.customer.email)  // NullPointerException here!
}

// GOOD - Validate upfront
function processOrder(order) {
    if (order == null) throw new Error("Order is required")
    if (order.customer?.email == null) throw new Error("Customer email is required")
    
    // Safe to proceed
}

Read the full file on GitHub · 109 lines

Changes

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.

  1. yesterday First seen · 109 lines · 24 tokens per session scan A 673893b12ffa

Subscribe to this mod's changes

clean-code-hygiene is a cursor rule published in the GitHub repository GoranErhartic/cursor-development-rules (19 stars, last pushed 6mo ago), licensed MIT. It adds 24 tokens to every session and 794 once invoked, about $0.0001 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-09-03.