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-api)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/quality-review-api"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/quality-review-api.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.1 | $0.00022 | $0.01207 |
| Opus 5 | $0.00011 | $0.00603 |
| Sonnet 5 | $0.00004 | $0.00241 |
| Haiku 4.5 | $0.00002 | $0.00121 |
Grade A, and why
quality-review-api 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 7d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
title: API Endpoint Review & Creation description: Comprehensive prompt for creating and reviewing API routes following Next.js 15 App Router standards tags: [prompt, api-routes, next.js, typescript, testing, security, validation] version: 1.0.0 lastUpdated: 2025-06-02 usage: Use for creating new API endpoints or reviewing existing ones audience: [claude, ai-assistants] scope: [api-design, security, validation, testing, error-handling, documentation]
API Endpoint Review & Creation Request
Please create or review API endpoints following our Next.js 15 App Router standards and security best practices:
API Design Requirements
1. Route Structure
- Use App Router convention:
app/api/[endpoint]/route.ts - Follow RESTful patterns where appropriate
- Use descriptive, resource-based URLs
- Implement proper HTTP methods (GET, POST, PUT, DELETE, PATCH)
2. Request Handling
- Implement proper request validation using Zod schemas
- Handle all supported HTTP methods explicitly
- Parse request bodies, query parameters, and path parameters correctly
- Implement proper content-type handling
3. Response Format
- Return consistent response structures
- Use appropriate HTTP status codes
- Include proper error messages and details
- Implement standardized success/error response format
Security Implementation
4. Authentication & Authorization
- Implement JWT token validation where required
- Check user permissions for protected endpoints
- Handle unauthenticated and unauthorized requests properly
- Validate token expiration and integrity
5. Input Validation & Sanitization
- Validate all input parameters using Zod schemas
- Sanitize user input to prevent XSS attacks
- Implement rate limiting where appropriate
- Protect against SQL injection and other common attacks
6. CORS & Headers
- Set appropriate CORS headers
- Implement security headers (CSP, etc.)
- Handle preflight OPTIONS requests
- Set proper cache control headers
Error 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.
- 7d ago First seen · 197 lines · 22 tokens per session scan A 98c375869dd8
quality-review-api is a cursor rule published in the GitHub repository oakensoul/nextjs-cursor-prompts (4 stars, last pushed 1y ago), licensed MIT. It adds 22 tokens to every session and 1,207 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
proxy-auth-transport
Every CLI command or browser UI action that calls a crit-web API must work in both modes.
api-design
API design guidelines — REST principles, GraphQL patterns, versioning, pagination, error handling, documentation, security, caching, and testing. Applied when designing or reviewing API endpoints.
api-ref-ffs-styleguide
Firefly Services API Style Guide checkpoints for api-eval (not api-fix).
architecture-guidelines
Guide cross-boundary, shared-module, API, data-flow, refactor, and long-lived design changes.
java-backend
Java Backend Execution Agent (Spring Boot / Quarkus).
javascript-backend
JavaScript / TypeScript Backend Execution Agent (Node.js / Express / Fastify / NestJS).