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-developergit clone --depth 1 https://github.com/oakensoul/nextjs-cursor-promptsWhat 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.06963 |
| Opus 5 | $0.00000 | $0.03481 |
| Sonnet 5 | $0.00000 | $0.01393 |
| Haiku 4.5 | $0.00000 | $0.00696 |
Grade C, and why
documentation-create-developer scanned grade C with 1 finding 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 2d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf node_modules yarn.lock How it starts
The opening of the file, as written. The whole thing — 977 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Documentation Creation
This prompt generates comprehensive developer-focused documentation including development environment setup, architecture overviews, coding standards, contribution guidelines, and technical workflows.
🎯 DEVELOPER DOCUMENTATION OBJECTIVES:
- ANALYZE codebase structure and generate setup documentation
- CREATE comprehensive developer guides for onboarding and contribution
- DOCUMENT architecture decisions and system design patterns
- ESTABLISH coding standards and development workflows
- GENERATE contribution guidelines and collaboration processes
🔧 DEVELOPMENT ENVIRONMENT ANALYSIS:
STEP 1: Technology Stack Discovery
Automated Stack Detection:
# Analyze project technology stack
echo "🔍 Analyzing Technology Stack..."
# Package managers and dependencies
echo "## Package Management:"
[ -f "package.json" ] && echo "- Node.js project (package.json found)"
[ -f "yarn.lock" ] && echo "- Yarn package manager"
[ -f "package-lock.json" ] && echo "- NPM package manager"
[ -f "pnpm-lock.yaml" ] && echo "- PNPM package manager"
[ -f "requirements.txt" ] && echo "- Python project (requirements.txt found)"
[ -f "Pipfile" ] && echo "- Python project with Pipenv"
[ -f "pyproject.toml" ] && echo "- Python project with Poetry"
[ -f "Gemfile" ] && echo "- Ruby project (Gemfile found)"
[ -f "Cargo.toml" ] && echo "- Rust project (Cargo.toml found)"
[ -f "go.mod" ] && echo "- Go project (go.mod found)"
# Framework detection
echo -e "\n## Frameworks and Libraries:"
if [ -f "package.json" ]; then
grep -q "next" package.json && echo "- Next.js framework"
grep -q "react" package.json && echo "- React library"
grep -q "vue" package.json && echo "- Vue.js framework"
grep -q "angular" package.json && echo "- Angular framework"
grep -q "express" package.json && echo "- Express.js server"
grep -q "fastify" package.json && echo "- Fastify server"
grep -q "gatsby" package.json && echo "- Gatsby framework"
grep -q "nuxt" package.json && echo "- Nuxt.js framework"
fi
# Development tools
echo -e "\n## Development Tools:"
[ -f "tsconfig.json" ] && echo "- TypeScript configuration"
[ -f ".eslintrc.js" ] || [ -f ".eslintrc.json" ] && echo "- ESLint linting"
[ -f "prettier.config.js" ] || [ -f ".prettierrc" ] && echo "- Prettier formatting"
[ -f "vitest.config.ts" ] && echo "- Vitest testing framework"
[ -f "jest.config.js" ] && echo "- Jest testing framework"
[ -f "cypress.config.js" ] && echo "- Cypress E2E testing"
[ -f "playwright.config.ts" ] && echo "- Playwright testing"
[ -f "tailwind.config.js" ] && echo "- Tailwind CSS"
[ -f "vite.config.ts" ] && echo "- Vite build tool"
[ -f "webpack.config.js" ] && echo "- Webpack bundler"
# Database and storage
echo -e "\n## Database and Storage:"
[ -f "prisma/schema.prisma" ] && echo "- Prisma ORM"
[ -f "drizzle.config.ts" ] && echo "- Drizzle ORM"
[ -f "knexfile.js" ] && echo "- Knex.js query builder"
grep -q "mongoose" package.json 2>/dev/null && echo "- MongoDB with Mongoose"
grep -q "pg" package.json 2>/dev/null && echo "- PostgreSQL"
grep -q "mysql" package.json 2>/dev/null && echo "- MySQL"
# Deployment and infrastructure
echo -e "\n## Deployment and Infrastructure:"
[ -f "Dockerfile" ] && echo "- Docker containerization"
[ -f "docker-compose.yml" ] && echo "- Docker Compose"
[ -f "vercel.json" ] && echo "- Vercel deployment"
[ -f "netlify.toml" ] && echo "- Netlify deployment"
[ -d ".github/workflows" ] && echo "- GitHub Actions CI/CD"
[ -f ".gitlab-ci.yml" ] && echo "- GitLab CI"
[ -f "serverless.yml" ] && echo "- Serverless framework"
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.
- 2d ago First seen · 977 lines · 0 tokens per session scan C 45a10cabf5bf
documentation-create-developer 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,963 tokens. A static security scan graded it C with 1 finding (recursive force delete). 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.
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.
family-instance-domain-actions
Family instance domain action implementation patterns.