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/patrickjs/awesome-cursorrules/codequalitygit clone --depth 1 https://github.com/PatrickJS/awesome-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.00000 | $0.00264 |
| Opus 5 | $0.00000 | $0.00132 |
| Sonnet 5 | $0.00000 | $0.00053 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
codequality 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- codequality — 100% identical, 2 lines differ
- code_quality — 94% identical, 6 lines differ
- codequality — 94% identical, 7 lines differ
- Code-quality — 94% identical, 20 lines differ
- codequality — 92% identical, 9 lines differ
- codequality — 92% identical, 9 lines differ
- codequality — 92% identical, 4 lines differ
- codequality — 92% identical, 9 lines differ
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.
- 2d ago First seen · 49 lines · 0 tokens per session scan A a10470d81da0
codequality is a cursor rule published in the GitHub repository PatrickJS/awesome-cursorrules (40,694 stars, last pushed 3mo ago), licensed CC0-1.0. It costs nothing until one of its globs matches a file; then it loads 264 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
snyk_rules
Snyk Security At Inception.
cursorrules
// Good: Use anyhow for application errors use anyhow::{Context, Result}.
creating-cursor-rules
Meta-rule for creating effective Cursor IDE rules with best practices, patterns, and examples.
prpm-json-best-practices
Best practices for structuring prpm.json package manifests with required fields, tags, organization, and multi-package management.
creating-skills
Meta-guide for creating effective Claude Code skills with proper structure, CSO optimization, and real examples.
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.