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/mitas/cursor-rulesWrote 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/mitas/cursor-rules/coding-principles)<a href="https://agentmods.dev/rules/mitas/cursor-rules/coding-principles"><img src="https://agentmods.dev/badge/rules/mitas/cursor-rules/coding-principles/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/mitas/cursor-rules/coding-principles"><img src="https://agentmods.dev/badge/rules/mitas/cursor-rules/coding-principles.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.00767 | $0.00767 |
| Opus 5.5 | $0.00307 | $0.00307 |
| Sonnet 5.5 | $0.00153 | $0.00153 |
| Haiku 4.5 | $0.00077 | $0.00077 |
Grade A, and why
coding-principles 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Quality Principles
Context
- Writing maintainable, readable code is a priority over clever optimizations
- Step-by-step implementation reduces errors and improves code quality
- Proper documentation and comments enhance long-term maintainability
- Following established coding standards improves collaboration
- The Unix philosophy of "do one thing well" leads to more robust solutions
Critical rules
- Proceed with small, focused steps instead of large, complex changes
- Always prioritize code readability and clarity over premature optimization
- Add explanatory comments to any complex or non-obvious logic
- Document all exported methods, functions, classes, and constants with purpose and usage notes
- Follow the established coding standards and conventions specific to the language in use
- Prefer simple, straightforward solutions over complex implementations
- Design components to do one thing well rather than multiple responsibilities
- Use descriptive variable and function names that reveal intent
- Break complex operations into smaller, focused functions
- Keep functions short and focused on a single responsibility
- Avoid deep nesting of control structures when possible
- Use consistent formatting throughout the codebase
- Apply the appropriate error handling approach for the language
- Include tests for new functionality when applicable
- Refactor duplicated code into reusable functions
Examples
/**
- Authenticates a user with provided credentials
- @param {string} username - The user's username
- @param {string} password - The user's password
- @returns {Promise} - The authenticated user or throws an error */ export async function authenticateUser(username, password) { // Validate inputs if (!username || !password) { throw new Error('Username and password required'); }
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 · 105 lines · 767 tokens per session scan A 782e6354f7d4
coding-principles is a cursor rule published in the GitHub repository mitas/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It adds 767 tokens to every session, about $0.0031 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-08-31.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).