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/documentation-create-fullgit 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/documentation-create-full)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/documentation-create-full"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/documentation-create-full.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.00000 | $0.05701 |
| Opus 5 | $0.00000 | $0.02851 |
| Sonnet 5 | $0.00000 | $0.01140 |
| Haiku 4.5 | $0.00000 | $0.00570 |
Grade A, and why
documentation-create-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 4d 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 — 727 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Comprehensive Documentation Creation Orchestrator
This prompt orchestrates complete documentation generation across all project dimensions including user guides, API documentation, developer resources, and architecture documentation with coordinated delivery and maintenance planning.
🎯 COMPREHENSIVE DOCUMENTATION OBJECTIVES:
- ORCHESTRATE multi-faceted documentation creation across all project stakeholders
- COORDINATE specialized documentation prompts with consistent methodology and standards
- CONSOLIDATE deliverables into cohesive, navigable documentation ecosystem
- ESTABLISH documentation baseline with quality metrics and maintenance workflows
- GENERATE documentation roadmap with priorities and resource planning
📋 DOCUMENTATION CREATION ORCHESTRATION:
STEP 1: Pre-Creation Assessment and Planning
Documentation Scope and Planning:
# Initialize comprehensive documentation creation
echo "📝 Initializing Comprehensive Documentation Creation"
echo "================================================="
# Create documentation workspace
DOCUMENTATION_DATE=$(date +"%Y%m%d_%H%M%S")
DOCUMENTATION_DIR="documentation_creation_${DOCUMENTATION_DATE}"
mkdir -p "$DOCUMENTATION_DIR"/{deliverables,artifacts,staging,final}
echo "📁 Documentation workspace: $DOCUMENTATION_DIR"
echo "📅 Creation date: $(date)"
echo "👤 Created by: $(git config user.name) <$(git config user.email)>"
echo "📂 Project: $(basename $(pwd))"
# Project documentation inventory
echo -e "\n🏗️ Project Documentation 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)"
# Existing documentation audit
echo -e "\n📚 Existing Documentation Audit:"
[ -f "README.md" ] && echo "- Main README found"
[ -d "docs/" ] && echo "- Docs directory exists ($(find docs/ -name "*.md" 2>/dev/null | wc -l) markdown files)"
[ -f "CHANGELOG.md" ] && echo "- Changelog present"
[ -f "CONTRIBUTING.md" ] && echo "- Contributing guidelines found"
[ -f "CODE_OF_CONDUCT.md" ] && echo "- Code of conduct present"
[ -f "LICENSE" ] && echo "- License file found"
[ -f "package.json" ] && echo "- Package.json with potential description"
[ -f "openapi.yaml" ] || [ -f "openapi.json" ] && echo "- OpenAPI specification found"
# Technology stack documentation requirements
echo -e "\n🛠️ Technology Stack Documentation Needs:"
[ -f "package.json" ] && echo "- Node.js/JavaScript documentation required"
[ -f "tsconfig.json" ] && echo "- TypeScript configuration documentation needed"
[ -f "next.config.js" ] && echo "- Next.js framework documentation required"
[ -f "tailwind.config.js" ] && echo "- Tailwind CSS documentation needed"
[ -f "vitest.config.ts" ] && echo "- Testing framework documentation required"
[ -f "cypress.config.js" ] && echo "- E2E testing documentation needed"
[ -f ".eslintrc*" ] && echo "- Code standards documentation required"
[ -f "docker-compose.yml" ] && echo "- Deployment documentation needed"
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.
- 4d ago First seen · 727 lines · 0 tokens per session scan A d31143e4460b
documentation-create-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 5,701 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
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.