cursorrules

A set of project-wide coding rules for Cursor, an AI code editor. It guides every file change with principles such as minimal edits, security checks, and a consistent response format.

In plain words
What is it for?
Use it to set shared rules for code changes, clarify assumptions, review file paths and verification steps, and prevent unsafe edits.
Why use it?
It reduces unnecessary refactoring and makes the agent stop when a request is unclear, risky, or could expose secrets.

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/zoxknez/ai-coding-rules/cursorrules
Clone the repo
git clone --depth 1 https://github.com/zoxknez/ai-coding-rules

Made for: Cursor.

Per session 108 This file is loaded in full into every session.
When invoked 108 The same file — it is already loaded in full.
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.00108 $0.00108
Opus 5 $0.00054 $0.00054
Sonnet 5 $0.00022 $0.00022
Haiku 4.5 $0.00011 $0.00011

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

Security

Grade A, and why

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

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

examples/modular-structure/.cursorrules · 18 lines

What it actually says

Root Rules (Minimal Global)

Load for every file in project (~300 tokens)

Core Principles

  • Correctness > simplicity > consistency > style
  • Minimal diff: touch only what's needed
  • No drive-by refactors

Non-Negotiables

  • Ask when ambiguous (assumptions + max 3 questions)
  • Stop on security, data loss, or breaking changes
  • No secrets in code

Output Format

  1. Brief plan
  2. Changes with file paths
  3. Verification steps
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 · 18 lines · 108 tokens per session scan A b45e5cd4913b

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository zoxknez/ai-coding-rules (27 stars, last pushed 4mo ago), licensed MIT. It adds 108 tokens to every session, about $0.0005 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-08-30.