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/code-guidelines-cursorrules-prompt-file)<a href="https://agentmods.dev/rules/patrickjs/awesome-cursorrules/code-guidelines-cursorrules-prompt-file"><img src="https://agentmods.dev/badge/rules/patrickjs/awesome-cursorrules/code-guidelines-cursorrules-prompt-file/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/patrickjs/awesome-cursorrules/code-guidelines-cursorrules-prompt-file"><img src="https://agentmods.dev/badge/rules/patrickjs/awesome-cursorrules/code-guidelines-cursorrules-prompt-file.svg" alt="Reviewed on agentmods" width="80" 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.00562 | $0.00562 |
| Opus 5.5 | $0.00225 | $0.00225 |
| Sonnet 5.5 | $0.00112 | $0.00112 |
| Haiku 4.5 | $0.00056 | $0.00056 |
Grade A, and why
code-guidelines-cursorrules-prompt-file 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 1mo 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
1 near-identical copy found in the catalogue:
- code-guidelines — 91% identical, 7 lines differ
What it actually says
-
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 the context generated file.
-
No Current Implementation: Don't show or discuss the current implementation unless specifically requested.
-
Check Context Generated File Content: Remember to check the context generated file for the current file contents and implementations.
-
Use Explicit Variable Names: Prefer descriptive, explicit variable names over short, ambiguous ones to enhance code readability.
-
Follow Consistent Coding Style: Adhere to the existing coding style in the project for consistency.
-
Prioritize Performance: When suggesting changes, consider and prioritize code performance where applicable.
-
Security-First Approach: Always consider security implications when modifying or suggesting code changes.
-
Test Coverage: Suggest or include appropriate unit tests for new or modified code.
-
Error Handling: Implement robust error handling and logging where necessary.
-
Modular Design: Encourage modular design principles to improve code maintainability and reusability.
-
Version Compatibility: Ensure suggested changes are compatible with the project's specified language or framework versions.
-
Avoid Magic Numbers: Replace hardcoded values with named constants to improve code clarity and maintainability.
-
Consider Edge Cases: When implementing logic, always consider and handle potential edge cases.
-
Use Assertions: Include assertions wherever possible to validate assumptions and catch potential errors early.
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.
- 1mo ago First seen · 57 lines · 0 tokens per session scan A eaa39ca88196
code-guidelines-cursorrules-prompt-file is a cursor rule published in the GitHub repository PatrickJS/awesome-cursorrules (40,971 stars, last pushed 4mo ago), licensed CC0-1.0. It adds 562 tokens to every session, about $0.0022 per session on Opus 5.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-30.
Other cursor rules, from other repositories
snyk_rules
Snyk Security At Inception.
cursorrules
// Good: Use anyhow for application errors use anyhow::{Context, Result}.
mobx-react-lite-usage
A set of rules for connecting MobX to React function components through mobx-react-lite, a library that makes components observe MobX state.
react-chakra-ui---typescript-usage
Guidance for using TypeScript with Chakra UI components in React. It covers typed component props, custom themes, editor support, and avoiding the unsafe any type.
typescript-code-generation-rules
A set of rules for writing React components in Next.js 14 with TypeScript, including typed props, function components, and export conventions.
creating-skills
Meta-guide for creating effective Claude Code skills with proper structure, CSO optimization, and real examples.