coding-style

coding-style is a cursor rule for Cursor from fmflurry/settings-opencode. It costs 1,124 tokens per session, scanned A, original, MIT.

A coding-style rule that requires creating new objects instead of changing existing ones, along with small focused files, explicit error handling, and input validation.

In plain words
What is it for?
It guides immutable updates, file organization, boundary checks for outside data, error messages, and server-side error logging.
Why use it?
Avoiding in-place changes reduces hidden side effects, while validation and explicit errors make failures easier to understand and debug.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit It guides immutable updates, file organization, boundary checks for outside data, error messages, and server-side error logging.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/fmflurry/settings-opencode/coding-style
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.

Clone the repo
git clone --depth 1 https://github.com/fmflurry/settings-opencode

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 coding-style

README.md
[![agentmods](https://agentmods.dev/badge/rules/fmflurry/settings-opencode/coding-style/github.svg)](https://agentmods.dev/rules/fmflurry/settings-opencode/coding-style)
Your own site
<a href="https://agentmods.dev/rules/fmflurry/settings-opencode/coding-style"><img src="https://agentmods.dev/badge/rules/fmflurry/settings-opencode/coding-style/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.

agentmods 80×15 button for coding-style

Your own site · 80×15
<a href="https://agentmods.dev/rules/fmflurry/settings-opencode/coding-style"><img src="https://agentmods.dev/badge/rules/fmflurry/settings-opencode/coding-style.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,124 This file is loaded in full into every session.
When invoked 1,124 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.01124 $0.01124
Opus 5.5 $0.00450 $0.00450
Sonnet 5.5 $0.00225 $0.00225
Haiku 4.5 $0.00112 $0.00112

Measured 8d ago against content hash 8021ae276983, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

coding-style 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 8d 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.

plugins/fmflurry-harness/rules/coding-style.mdc · 190 lines

How it starts

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

Coding Style

Immutability (CRITICAL)

ALWAYS create new objects, NEVER mutate existing ones:

// Pseudocode
WRONG:  modify(original, field, value) → changes original in-place
CORRECT: update(original, field, value) → returns new copy with change

Rationale: Immutable data prevents hidden side effects, makes debugging easier, and enables safe concurrency.

File Organization

MANY SMALL FILES > FEW LARGE FILES:

  • High cohesion, low coupling
  • 200-400 lines typical, 800 max
  • Extract utilities from large modules
  • Organize by feature/domain, not by type

Error Handling

ALWAYS handle errors comprehensively:

  • Handle errors explicitly at every level
  • Provide user-friendly error messages in UI-facing code
  • Log detailed error context on the server side
  • Never silently swallow errors

Input Validation

ALWAYS validate at system boundaries:

  • Validate all user input before processing
  • Use schema-based validation where available
  • Fail fast with clear error messages
  • Never trust external data (API responses, user input, file content)

Core Principles

KISS (Keep It Simple, Stupid): Simplest solution that works. Avoid over-engineering. No premature optimization. Easy to understand beats clever code.

DRY (Don't Repeat Yourself): Extract common logic. Create reusable components. Share utilities. Avoid copy-paste programming.

YAGNI (You Aren't Gonna Need It): Don't build before needed. Avoid speculative generality. Add complexity only when required.

Naming Conventions

Descriptive names: Variable and function names should be self-documenting. Choose clear over clever.

// Good: Descriptive
const marketSearchQuery = "election";
const isUserAuthenticated = true;

// Bad: Unclear
const q = "election";
const flag = true;

Function naming: Use verb-noun pattern. Names read like actions.

// Good
async function fetchMarketData(id: string) {}
function calculateSimilarity(a: number[], b: number[]) {}
function isValidEmail(email: string): boolean {}

// Bad
async function market(id: string) {}
function similarity(a, b) {}

Read the full file on GitHub · 190 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. 8d ago First seen · 190 lines · 1,124 tokens per session scan A 8021ae276983

Subscribe to this mod's changes

coding-style is a cursor rule published in the GitHub repository fmflurry/settings-opencode (171 stars, last pushed yesterday), licensed MIT. It adds 1,124 tokens to every session, about $0.0045 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-10-08.