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/oakensoul/nextjs-cursor-prompts/quality-review-codegit 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-code)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/quality-review-code"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/quality-review-code.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.00019 | $0.01490 |
| Opus 5 | $0.00010 | $0.00745 |
| Sonnet 5 | $0.00004 | $0.00298 |
| Haiku 4.5 | $0.00002 | $0.00149 |
Grade A, and why
quality-review-code 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 5d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
title: Code Quality & Testing Review description: Comprehensive prompt for ensuring code meets project standards with appropriate documentation and testing tags: [prompt, code-quality, testing, documentation, standards] version: 2.0.0 lastUpdated: 2025-06-02 usage: Reference this prompt for any file or directory that needs quality review audience: [claude, ai-assistants] scope: [documentation, unit-testing, accessibility-testing, integration-testing]
Code Quality & Testing Request
IMPORTANT: This prompt requires completing ALL applicable tasks listed below. Do not skip any sections without explicitly explaining why.
FOLLOW MINIMAL CHANGE PRINCIPLES: When creating tests and documentation, preserve existing code patterns and architecture. Do not rewrite working code unnecessarily.
Please review the code I'm working on and ensure it meets our project standards. Based on the file types and functionality, determine which tasks are applicable:
Documentation Tasks
1. Update inline code documentation
- Add/update JSDoc comments for all functions, components, and interfaces
- Ensure parameters and return types are documented with descriptions
- Document any complex logic or business rules
- Add usage examples where helpful
2. Developer README.md
- Evaluate if this code warrants its own README.md documentation
- Create or update if it's a significant component, feature, or standalone module
- Include: purpose, API/props, usage examples, and any special considerations
Testing Tasks
3. Unit Tests (evaluate applicability)
- For Components: Test rendering, props, user interactions, error/loading states
- For Server Actions: Test success cases, error handling, input validation
- For API Routes: Test endpoints, request/response handling, authentication
- For Utilities/Hooks: Test function behavior, edge cases, error conditions
- Create appropriate test files following our vitest standards
- Ensure 80%+ coverage
4. Accessibility Tests (evaluate applicability)
- MANDATORY for ALL UI components that render visual elements to the DOM
- Required for: Buttons, forms, navigation, modals, cards, layouts, any interactive elements
- Skip for: Server actions, API routes, utilities, hooks, non-visual components, data services
- Use vitest-axe to test for violations and keyboard navigation
- Create separate
.a11y.test.tsxfiles (NOT combined with unit tests) - Test all component variants and states for accessibility compliance
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.
- 5d ago First seen · 153 lines · 19 tokens per session scan A 04ba7e3925af
quality-review-code is a cursor rule published in the GitHub repository oakensoul/nextjs-cursor-prompts (4 stars, last pushed 1y ago), licensed MIT. It adds 19 tokens to every session and 1,490 once invoked, about $0.0001 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.
family-instance-domain-actions
Family instance domain action implementation 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.