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/tyrchen/cursor-rust-rules/code-qualitygit clone --depth 1 https://github.com/tyrchen/cursor-rust-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.00000 | $0.02083 |
| Opus 5 | $0.00000 | $0.01042 |
| Sonnet 5 | $0.00000 | $0.00417 |
| Haiku 4.5 | $0.00000 | $0.00208 |
Grade A, and why
code-quality 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 2d 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 — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🦀 RUST CORE CODE QUALITY STANDARDS
TL;DR: Essential code quality rules for all Rust projects, focusing on maintainable, production-ready code that follows modern Rust 2024 idioms.
🔍 CODE QUALITY STRATEGY SELECTION
graph TD
Start["Code Quality Requirements"] --> ProjectType{"Project Type?"}
ProjectType -->|"Simple Library"| SimpleLib["Simple Library Rules"]
ProjectType -->|"Complex Application"| ComplexApp["Complex Application Rules"]
ProjectType -->|"CLI Tool"| CLITool["CLI Tool Rules"]
ProjectType -->|"Web Service"| WebService["Web Service Rules"]
SimpleLib --> BasicRules["Basic Quality Rules"]
ComplexApp --> AdvancedRules["Advanced Quality Rules"]
CLITool --> BasicRules
WebService --> AdvancedRules
BasicRules --> Naming["Naming Strategy"]
AdvancedRules --> Naming
Naming --> NamingRules["• Functionality-based files<br>• Descriptive specific names<br>• No implementation suffixes"]
NamingRules --> Structure["Code Structure"]
Structure --> StructureRules["• File-based organization<br>• Size limitations (500 lines)<br>• Single responsibility<br>• Function size (150 lines)"]
StructureRules --> Safety["Safety Requirements"]
Safety --> SafetyRules["• Rust 2024 edition<br>• No unsafe code<br>• No unwrap() in production<br>• Proper error handling"]
SafetyRules --> Testing["Testing Strategy"]
Testing --> TestingRules["• Unit tests same file<br>• Integration tests separate<br>• Doc tests with examples"]
TestingRules --> Verification["Quality Verification"]
Verification --> Build["cargo build"]
Verification --> Test["cargo test"]
Verification --> Clippy["cargo clippy"]
Build --> AllPass{"All Pass?"}
Test --> AllPass
Clippy --> AllPass
AllPass -->|"Yes"| Success["✅ Quality Standards Met"]
AllPass -->|"No"| FixIssues["🔧 Fix Issues"]
FixIssues --> Verification
style Start fill:#4da6ff,stroke:#0066cc,color:white
style ProjectType fill:#ffa64d,stroke:#cc7a30,color:white
style SimpleLib fill:#4dbb5f,stroke:#36873f,color:white
style ComplexApp fill:#d94dbb,stroke:#a3378a,color:white
style CLITool fill:#9f4dbb,stroke:#7a3787,color:white
style WebService fill:#bb4d4d,stroke:#873636,color:white
style BasicRules fill:#bbbb4d,stroke:#878736,color:white
style AdvancedRules fill:#4dbbbb,stroke:#368787,color:white
style Success fill:#5fbb5f,stroke:#4a8f4a,color:white
style FixIssues fill:#ff6b6b,stroke:#cc5555,color:white
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.
- 2d ago First seen · 297 lines · 0 tokens per session scan A 1c675834b3f8
code-quality is a cursor rule published in the GitHub repository tyrchen/cursor-rust-rules (27 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,083 tokens. 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.
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.