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/tonynguyennvt/cursor-rules-awesome/cursorrulesgit clone --depth 1 https://github.com/tonynguyennvt/cursor-rules-awesomeWrote 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/tonynguyennvt/cursor-rules-awesome/cursorrules)<a href="https://agentmods.dev/rules/tonynguyennvt/cursor-rules-awesome/cursorrules"><img src="https://agentmods.dev/badge/rules/tonynguyennvt/cursor-rules-awesome/cursorrules.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 | $0.36510 | $0.36510 |
| Opus 5 | $0.18255 | $0.18255 |
| Sonnet 5 | $0.07302 | $0.07302 |
| Haiku 4.5 | $0.03651 | $0.03651 |
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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 4,862 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor AI Assistant Rules - Comprehensive Coding Standards
Version: 1.0
Last Updated: 2025-10-19
Total Sections: 72
Lines: 4,800+
Compliance: ISO 27001, OWASP Top 10, GDPR, SOC 2, HIPAA, PCI-DSS
TABLE OF CONTENTS
PART I: FOUNDATIONS (Sections 1-21)
- Code Quality & Best Practices
- Performance & Optimization
- Security
- Testing
- Error Handling & Logging
- Code Organization & Architecture
- Documentation
- Version Control
- Accessibility
- Internationalization & Localization
- Professionalism
- File & Folder Organization
- Dependency Management
- Build & Deployment
- Production Operations & Maintenance
- Code Review
- Special Instructions
- Naming Conventions
- Comments
- Code Formatting
- Database Design & Optimization
PART II: DATA & BACKEND (Sections 22-26)
- NoSQL Databases
- Firebase Best Practices
- Authentication & Authorization
- GraphQL Best Practices
- Microservices & Distributed Systems
PART III: INFRASTRUCTURE (Sections 27-31)
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.
- 4d ago First seen · 4,862 lines · 36,510 tokens per session scan A e3206c5e97a1
cursorrules is a cursor rule published in the GitHub repository tonynguyennvt/cursor-rules-awesome (5 stars, last pushed 10mo ago), licensed MIT. It adds 36,510 tokens to every session, about $0.1825 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-08-31.
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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.