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-documentation)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/quality-review-documentation"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/quality-review-documentation/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-documentation"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/quality-review-documentation.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.04249 |
| Opus 5 | $0.00000 | $0.02124 |
| Sonnet 5 | $0.00000 | $0.00850 |
| Haiku 4.5 | $0.00000 | $0.00425 |
Grade A, and why
quality-review-documentation 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 8d 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 — 523 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Quality Review and Assessment
This prompt provides comprehensive evaluation of project documentation including technical docs, user guides, API documentation, and maintenance materials with actionable improvement recommendations.
🎯 DOCUMENTATION REVIEW OBJECTIVES:
- ASSESS documentation completeness across all project areas
- EVALUATE content quality including accuracy, clarity, and usefulness
- REVIEW structure and organization for logical flow and discoverability
- VALIDATE user experience from different audience perspectives
- IDENTIFY maintenance gaps and sustainability issues
📚 DOCUMENTATION INVENTORY AND ANALYSIS:
STEP 1: Documentation Discovery and Categorization
Automated Documentation Inventory:
# Discover all documentation files
echo "📋 Discovering project documentation..."
# Find markdown files
echo "## Markdown Documentation:"
find . -name "*.md" -not -path "./node_modules/*" -not -path "./.git/*" | sort
# Find documentation directories
echo -e "\n## Documentation Directories:"
find . -type d -name "*doc*" -o -name "*guide*" -o -name "*manual*" | grep -v node_modules | sort
# Find README files
echo -e "\n## README Files:"
find . -name "README*" -not -path "./node_modules/*" | sort
# Find API documentation
echo -e "\n## API Documentation:"
find . -name "*.yaml" -o -name "*.yml" -o -name "swagger*" -o -name "openapi*" | grep -v node_modules | sort
# Find JSDoc/TypeDoc files
echo -e "\n## Code Documentation:"
find . -name "*.jsdoc" -o -name "typedoc.json" | grep -v node_modules | sort
# Check for documentation generators
echo -e "\n## Documentation Tools:"
[ -f "package.json" ] && grep -E "(jsdoc|typedoc|docusaurus|vitepress|gitbook)" package.json || echo "No documentation tools found in package.json"
Documentation Categories Assessment:
## Documentation Categories Checklist
### Project Overview Documentation:
- [ ] **Main README.md** - Project introduction and quick start
- [ ] **CONTRIBUTING.md** - Contribution guidelines
- [ ] **CHANGELOG.md** - Version history and changes
- [ ] **LICENSE** - Legal and usage terms
- [ ] **CODE_OF_CONDUCT.md** - Community guidelines
### Technical Documentation:
- [ ] **Architecture Documentation** - System design and structure
- [ ] **API Documentation** - Endpoint specifications and examples
- [ ] **Database Schema** - Data model and relationships
- [ ] **Deployment Guides** - Installation and deployment procedures
- [ ] **Configuration Guides** - Environment setup and options
### User Documentation:
- [ ] **User Guides** - End-user instruction manuals
- [ ] **Tutorials** - Step-by-step learning materials
- [ ] **FAQ** - Frequently asked questions
- [ ] **Troubleshooting** - Problem resolution guides
- [ ] **Examples** - Working code samples and demos
### Developer Documentation:
- [ ] **Setup Instructions** - Development environment setup
- [ ] **Coding Standards** - Style guides and conventions
- [ ] **Testing Documentation** - Testing strategies and procedures
- [ ] **Security Guidelines** - Security best practices
- [ ] **Performance Guidelines** - Optimization recommendations
### Operational Documentation:
- [ ] **Monitoring Guides** - System monitoring and alerting
- [ ] **Backup Procedures** - Data backup and recovery
- [ ] **Disaster Recovery** - Business continuity plans
- [ ] **Runbooks** - Operational procedures
- [ ] **Incident Response** - Emergency response procedures
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.
- 8d ago First seen · 523 lines · 0 tokens per session scan A 221ad5b362e2
quality-review-documentation 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 4,249 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-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.