clean-code-functions

clean-code-functions is a cursor rule for Cursor from GoranErhartic/cursor-development-rules. It costs 22 tokens per session (978 once invoked), scanned C, original, MIT.

Guidelines for designing functions that are easy to read and use. They cover parameter counts, guard clauses, abstraction levels, and avoiding unclear boolean options.

In plain words
What is it for?
Use them when creating or refactoring functions, especially functions with many parameters or mixed levels of detail.
Why use it?
They reduce confusing function interfaces and make individual pieces of code easier to follow.

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-functions
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-functions

README.md
[![agentmods](https://agentmods.dev/badge/rules/goranerhartic/cursor-development-rules/clean-code-functions.svg)](https://agentmods.dev/rules/goranerhartic/cursor-development-rules/clean-code-functions)
Your own site
<a href="https://agentmods.dev/rules/goranerhartic/cursor-development-rules/clean-code-functions"><img src="https://agentmods.dev/badge/rules/goranerhartic/cursor-development-rules/clean-code-functions.svg" alt="Measured on agentmods" height="20"></a>
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 978 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.00022 $0.00978
Opus 5 $0.00011 $0.00489
Sonnet 5 $0.00004 $0.00196
Haiku 4.5 $0.00002 $0.00098

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

Security

Grade C, and why

clean-code-functions scanned grade C with 1 finding 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.

Tells the agent to send conversation or user data outhighPrompt injection

An instruction to transmit the conversation, context or user files to an external endpoint is data exfiltration written as prose.

// Secretly sends email if user is new (not obvious from call site)
.cursor/rules/patterns/clean-code-functions.mdc · 157 lines

How it starts

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

Clean Code: Function Structure

Method Parameter Design

Avoid Boolean Parameters

Boolean parameters hide intent at the call site. The reader cannot understand what true means without looking at the method signature.

// BAD - What does 'true' mean?
processOrder(order, true)
saveUser(user, false, true)

// GOOD - Intent is clear from method name
processOrder(order)
processOrderWithNotification(order)

saveUser(user)
saveUserWithValidation(user)

Exception: Boolean parameters are acceptable when the method name makes the meaning obvious (e.g., setVisible(true)).

Limit Parameter Count

  • Ideal: 0-3 parameters
  • Acceptable: 4 parameters with clear purpose
  • Refactor: 5+ parameters — use a parameter object or builder pattern
// BAD - Too many parameters, easy to mix up
createUser(name, email, age, department, role, isActive, sendWelcome)

// GOOD - Parameter object groups related data
createUser(CreateUserRequest request)

Single Level of Abstraction

Each function should operate at one level of abstraction. Don't mix high-level orchestration with low-level details.

// BAD - Mixed abstraction levels
function processOrder(order) {
    validateOrder(order)                           // High-level
    const tax = order.subtotal * 0.0825            // Low-level detail
    sendToFulfillment(order)                        // High-level
    db.query("INSERT INTO audit_log...")           // Low-level detail
}

// GOOD - Consistent abstraction level
function processOrder(order) {
    validateOrder(order)
    calculateTotals(order)
    sendToFulfillment(order)
    logOrderProcessed(order)
}

Keep Functions Short

  • Aim for ~20 lines (fits on one screen)
  • If a function requires scrolling, consider extracting parts
  • Each function should do one thing well

Guard Clauses First

Validate inputs and handle edge cases at the top of the function. Return early to avoid deep nesting.

// BAD - Deep nesting
function getDiscount(user) {
    if (user != null) {
        if (user.isActive) {
            if (user.membershipYears > 5) {
                return 0.20
            }
        }
    }
    return 0
}

// GOOD - Guard clauses with early returns
function getDiscount(user) {
    if (user == null) return 0
    if (!user.isActive) return 0
    if (user.membershipYears <= 5) return 0
    
    return 0.20
}

Read the full file on GitHub · 157 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 · 157 lines · 22 tokens per session scan C 0736d50fa415

Subscribe to this mod's changes

clean-code-functions is a cursor rule published in the GitHub repository GoranErhartic/cursor-development-rules (19 stars, last pushed 6mo ago), licensed MIT. It adds 22 tokens to every session and 978 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (tells the agent to send conversation or user data out). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.