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-full)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/quality-review-full"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/quality-review-full/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-full"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/quality-review-full.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.06216 |
| Opus 5 | $0.00000 | $0.03108 |
| Sonnet 5 | $0.00000 | $0.01243 |
| Haiku 4.5 | $0.00000 | $0.00622 |
Grade A, and why
quality-review-full 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 10d 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 — 703 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Comprehensive Quality Review Orchestrator
This prompt orchestrates a complete quality assessment across all project dimensions including code quality, security, accessibility, API design, SEO optimization, and documentation with consolidated reporting, prioritized action plans, and persistent quality documentation tracking.
🎯 COMPREHENSIVE REVIEW OBJECTIVES:
- ORCHESTRATE multi-dimensional quality assessment across all project areas
- COORDINATE specialized reviews with consistent methodology and standards
- CONSOLIDATE findings into actionable, prioritized improvement roadmap
- ESTABLISH quality baseline with measurable metrics and tracking
- GENERATE executive summary with business impact and resource planning
- CREATE persistent documentation in docs/quality-review/ for historical tracking
📋 QUALITY ASSESSMENT ORCHESTRATION:
STEP 1: Pre-Assessment Setup and Planning
Assessment Workspace and Documentation Setup:
# Initialize comprehensive quality assessment with documentation tracking
echo "🔍 Initializing Comprehensive Quality Assessment with Documentation Tracking"
echo "=========================================================================="
# Create assessment workspace AND persistent documentation
ASSESSMENT_DATE=$(date +"%Y%m%d_%H%M%S")
PROJECT_NAME=$(basename $(pwd))
ASSESSMENT_DIR="quality_assessment_${ASSESSMENT_DATE}"
DOCS_QUALITY_DIR="docs/quality-review"
# Create both temporary workspace and persistent documentation
mkdir -p "$ASSESSMENT_DIR"/{reports,artifacts,recommendations}
mkdir -p "$DOCS_QUALITY_DIR"/{reports,historical,summaries}
echo "📁 Temporary workspace: $ASSESSMENT_DIR"
echo "📚 Persistent documentation: $DOCS_QUALITY_DIR"
echo "📅 Assessment date: $(date)"
echo "👤 Assessed by: $(git config user.name) <$(git config user.email)>"
echo "📂 Project: $PROJECT_NAME"
# Project inventory
echo -e "\n🏗️ Project Overview:"
echo "Repository: $(git remote get-url origin 2>/dev/null || echo 'Local repository')"
echo "Current branch: $(git branch --show-current)"
echo "Last commit: $(git log -1 --oneline)"
echo "Files tracked: $(git ls-files | wc -l)"
# Technology stack detection
echo -e "\n🛠️ Technology Stack:"
[ -f "package.json" ] && echo "- Node.js/JavaScript project detected"
[ -f "tsconfig.json" ] && echo "- TypeScript configuration found"
[ -f "next.config.js" ] && echo "- Next.js framework detected"
[ -f "tailwind.config.js" ] && echo "- Tailwind CSS detected"
[ -f "vitest.config.ts" ] && echo "- Vitest testing framework detected"
[ -f "cypress.config.js" ] && echo "- Cypress E2E testing detected"
[ -f ".eslintrc*" ] && echo "- ESLint configuration found"
[ -f "prettier.config.js" ] && echo "- Prettier configuration found"
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.
- 10d ago First seen · 703 lines · 0 tokens per session scan A 3cb4fc484cfd
quality-review-full 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 6,216 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
clean-code-reviewer
Eliminates technical debt using SOLID, DRY, YAGNI, and Addy Osmani production-grade engineering principles. / TR: SOLID, DRY, YAGNI ve Addy Osmani üretim seviyesi mühendislik ilkeleri ile kod kalitesini denetleyen yetenek.
sweep-benchmarks
Audit xrspatial modules for asv benchmark coverage gaps: missing benchmarks, backend parameterization gaps, unrepresentative inputs, broken or silently-skipped benchmarks.
code-review
BMAD BMM Agent: code-review.
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.