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.
npx agentmods add rules/mitas/cursor-rules/coding-principlesgit clone --depth 1 https://github.com/mitas/cursor-rulesWhat 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 | $0.00767 | $0.00767 |
| Opus 5 | $0.00383 | $0.00383 |
| Sonnet 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 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.
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.
- yesterday 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.0038 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-31.
Other cursor rules, from other repositories
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.