PatrickJS/awesome-cursorrules is a collection of Markdown rule files that give Cursor AI editor project-specific instructions about code, frameworks, workflows, and standards. Developers use it to find reusable guidance for shaping Cursor’s behavior in different kinds of software projects.
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/PatrickJS/awesome-cursorrulesWrote 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/patrickjs/awesome-cursorrules/optimize-dry-solid-principles-cursorrules-prompt-f)<a href="https://agentmods.dev/rules/patrickjs/awesome-cursorrules/optimize-dry-solid-principles-cursorrules-prompt-f"><img src="https://agentmods.dev/badge/rules/patrickjs/awesome-cursorrules/optimize-dry-solid-principles-cursorrules-prompt-f.svg" alt="Measured on agentmods" 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.00150 | $0.00150 |
| Opus 5 | $0.00075 | $0.00075 |
| Sonnet 5 | $0.00030 | $0.00030 |
| Haiku 4.5 | $0.00015 | $0.00015 |
Grade A, and why
optimize-dry-solid-principles-cursorrules-prompt-f 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 3d 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.
What it actually says
Communication and Problem-Solving:
Code Quality and Best Practices:
Paradigms and Principles:
Semantic Naming and Abstractions:
Platform Thinking:
Response Format:
Handling Uncertainty and Limitations:
When outputting code blocks, include a # or // file name comment prior to the block, with a few lines before and after the modification. This helps the user identify where to make changes.
Stick to the current architecture choices located in pyproject.toml unless the user suggests a new method or module.
If you need clarification on any part of the task, ask for more information before proceeding with the implementation.
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.
- 3d ago First seen · 25 lines · 150 tokens per session scan A d2ff9e3dd28a
optimize-dry-solid-principles-cursorrules-prompt-f is a cursor rule published in the GitHub repository PatrickJS/awesome-cursorrules (40,732 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 150 tokens to every session, about $0.0007 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-09-03.
Other cursor rules, from other repositories
karen-repo-reviewer
Use Karen for brutally honest repository reviews with market-aware Karen Scores. Analyzes entire codebases for over-engineering, completion honesty, and whether the project actually solves a real problem.
refactoring
Refactoring: systematic approach, extract/inline, guard clauses, early returns.
clean-code
Clean code: naming, functions, simplicity.
code-review
Code review: reviewing approach, authoring PRs, feedback conventions.
git-workflow
Git workflow: commits, branches, PRs, history management.
snyk_rules
Snyk Security At Inception.