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/paulpham157/paul-s-cursor-rulesWrote 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/paulpham157/paul-s-cursor-rules/cursorrules)<a href="https://agentmods.dev/rules/paulpham157/paul-s-cursor-rules/cursorrules"><img src="https://agentmods.dev/badge/rules/paulpham157/paul-s-cursor-rules/cursorrules/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/paulpham157/paul-s-cursor-rules/cursorrules"><img src="https://agentmods.dev/badge/rules/paulpham157/paul-s-cursor-rules/cursorrules.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.00816 | $0.00816 |
| Opus 5.5 | $0.00326 | $0.00326 |
| Sonnet 5.5 | $0.00163 | $0.00163 |
| Haiku 4.5 | $0.00082 | $0.00082 |
Grade A, and why
cursorrules 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
2 near-identical copies found in the catalogue:
- cursorrules — 100% identical, 0 lines differ
- cursorrules — 100% identical, 0 lines differ
What it actually says
// Awesome CursorRules // A curated list of awesome .cursorrules files for enhancing Cursor AI experience
// General guidelines Always use Markdown for documentation and README files Maintain the existing structure of the README.md file
// README.md structure Maintain the following structure in the README.md file:
- Title and Awesome badge
- Logo
- Short description
- "Why .cursorrules?" section
- Table of Contents
- Rules section
- Frontend Frameworks and Libraries
- Backend and Full-Stack
- Mobile Development
- CSS and Styling
- State Management
- Database and API
- Testing
- Build Tools and Development
- Language-Specific
- Other
- How to Use section
- Contributing section
- License section
// Organization of rules Organize .cursorrules files into the following main categories within the 'rules' directory:
- Frontend Frameworks and Libraries
- Backend and Full-Stack
- Mobile Development
- CSS and Styling
- State Management
- Database and API
- Testing
- Build Tools and Development
- Language-Specific
- Other Place each .cursorrules file directly in the 'rules' folder The folder name for each .cursorrules file should describe the category and content of the file Refer to the README in each folder for guidance on naming conventions and descriptions
// Naming and formatting Use descriptive names for .cursorrules files and their folders, following the pattern: 'technology-focus-cursorrules-prompt-file' Maintain alphabetical order within each category in the README.md file Use consistent formatting for list items in the README.md file
// Content guidelines When creating or editing .cursorrules files, focus on project-specific instructions and best practices Include comments in .cursorrules files to explain complex rules or provide context Use clear and concise language in all documentation and .cursorrules files Provide context on what you're building, style guidelines, or info on commonly-used methods
// Optional README for credit and description Each .cursorrules file may have an accompanying README.md file in its folder Use this README to provide credit to the original author and a brief description of the .cursorrules file's purpose
// Maintenance and updates Update the README.md file when adding new .cursorrules files, placing them in the correct category Ensure all links in the README.md file are relative and correct When updating the README.md, ensure the table of contents remains accurate When adding new categories, update both the 'Contents' and 'Rules' sections of the README.md Regularly review and update categorization as the repository grows
// Best practices Maintain consistency in capitalization and punctuation throughout the repository When referencing Cursor AI, always use the correct capitalization and spacing When adding examples or explanations, focus on practical use cases for Cursor AI users If a .cursorrules file fits multiple categories, place it in the most relevant one and cross-reference in others if necessary Keep the 'Other' category for .cursorrules files that don't fit neatly into the main categories
// Additional insights .cursorrules files are repo-specific "Rules for AI" .cursorrules files should be placed in the root of the repository The content of .cursorrules files will be appended to the global "Rules for AI" settings in Cursor Focus on providing repo-level context and guidelines, not just general coding practices .cursorrules can include information about project structure, architectural decisions, and commonly used libraries or methods Consider including rules for handling specific file types or coding patterns unique to your project Rules can cover both code generation and code understanding aspects for Cursor AI
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 · 82 lines · 816 tokens per session scan A a958974cc6f7
cursorrules is a cursor rule published in the GitHub repository paulpham157/paul-s-cursor-rules (27 stars, last pushed 1y ago), licensed MIT. It adds 816 tokens to every session, about $0.0033 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
pyspark-etl-best-practices-cursorrules-prompt-file
Cursor rules for PySpark ETL development with code style, joins, window functions, map operations, and Iceberg patterns.
project-epic-template-cursorrules-prompt-file
Cursor rules for project development with epic template integration.
react-tanstack-router-query-cursorrules-prompt-file
Cursor rules for React SPAs combining TanStack Router v1 and TanStack Query v5 for zero-loading-spinner routing and type-safe server state.
ankra-cli
Ankra CLI rules and best practices for managing Kubernetes clusters via the Ankra platform.
playwright-integration-testing-cursorrules-prompt-file
Cursor rules for Playwright development with integration testing.
go-backend-scalability-cursorrules-prompt-file
Cursor rules for Go development with backend scalability.