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/oakensoul/nextjs-cursor-promptsWrote 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/oakensoul/nextjs-cursor-prompts/quality-review-security)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/quality-review-security"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/quality-review-security/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/oakensoul/nextjs-cursor-prompts/quality-review-security"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/quality-review-security.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.00000 | $0.03123 |
| Opus 5 | $0.00000 | $0.01562 |
| Sonnet 5 | $0.00000 | $0.00625 |
| Haiku 4.5 | $0.00000 | $0.00312 |
Grade A, and why
quality-review-security 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 9d 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 — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Review and Vulnerability Assessment Guide
This prompt provides comprehensive security auditing for code, APIs, and application components, identifying vulnerabilities and ensuring security best practices are implemented.
🎯 SECURITY REVIEW OBJECTIVES:
- IDENTIFY security vulnerabilities across all application layers
- ASSESS implementation of security best practices and standards
- EVALUATE data protection and privacy compliance measures
- VALIDATE authentication and authorization mechanisms
- PROVIDE actionable remediation recommendations with severity ratings
🔒 COMPREHENSIVE SECURITY ASSESSMENT:
STEP 1: Input Validation and Sanitization
Input Security Audit:
- SQL Injection Prevention - Parameterized queries, ORM usage, input validation
- XSS Protection - Output encoding, Content Security Policy, input sanitization
- Command Injection - Input validation, safe command execution patterns
- Path Traversal - File path validation, restricted file access
- LDAP Injection - Proper LDAP query construction and validation
Data Validation Checks:
- Type validation - Strict type checking for all inputs
- Length validation - Maximum input length enforcement
- Format validation - Regular expressions for data format checking
- Range validation - Numeric and date range checking
- Whitelist validation - Allowed values enumeration where applicable
Sanitization Implementation:
- HTML sanitization - Dangerous HTML element removal
- JavaScript sanitization - Script injection prevention
- File upload sanitization - File type, size, and content validation
- Database input cleaning - Special character handling
- API parameter sanitization - Request parameter validation
STEP 2: Authentication and Authorization Security
Authentication Mechanism Review:
- Password security - Hashing algorithms (bcrypt, Argon2), complexity requirements
- Multi-factor authentication - TOTP, SMS, email verification implementation
- Session management - Secure session tokens, expiration, invalidation
- OAuth implementation - Proper OAuth 2.0/OpenID Connect usage
- JWT security - Proper signing, validation, and expiration handling
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.
- 9d ago First seen · 345 lines · 0 tokens per session scan A 24511e2e9449
quality-review-security is a cursor rule published in the GitHub repository oakensoul/nextjs-cursor-prompts (4 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,123 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-31.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.