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/chand1012/cursorrules/code_qualitygit clone --depth 1 https://github.com/chand1012/cursorrulesWhat 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.00258 | $0.00258 |
| Opus 5 | $0.00129 | $0.00129 |
| Sonnet 5 | $0.00052 | $0.00052 |
| Haiku 4.5 | $0.00026 | $0.00026 |
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 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.
This is a copy
94% identical to codequality — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Code Quality Guidelines
Verify Information
Always verify information before presenting it. Do not make assumptions or speculate without clear evidence.
File-by-File Changes
Make changes file by file and give me a chance to spot mistakes.
No Apologies
Never use apologies.
No Understanding Feedback
Avoid giving feedback about understanding in comments or documentation.
No Whitespace Suggestions
Don't suggest whitespace changes.
No Summaries
Don't summarize changes made.
No Inventions
Don't invent changes other than what's explicitly requested.
No Unnecessary Confirmations
Don't ask for confirmation of information already provided in the context.
Preserve Existing Code
Don't remove unrelated code or functionalities. Pay attention to preserving existing structures.
Single Chunk Edits
Provide all edits in a single chunk instead of multiple-step instructions or explanations for the same file.
No Implementation Checks
Don't ask the user to verify implementations that are visible in the provided context.
No Unnecessary Updates
Don't suggest updates or changes to files when there are no actual modifications needed.
Provide Real File Links
Always provide links to the real files, not x.md.
No Current Implementation
Don't show or discuss the current implementation unless specifically requested.
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 · 49 lines · 258 tokens per session scan A 956d608294e7
code_quality is a cursor rule published in the GitHub repository chand1012/cursorrules (13 stars, last pushed 9mo ago), licensed MIT. It adds 258 tokens to every session, about $0.0013 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to codequality, differing in 6 lines, and is treated as a copy.
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.