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-update-developergit 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-update-developer)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/documentation-update-developer"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/documentation-update-developer.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.02392 |
| Opus 5 | $0.00000 | $0.01196 |
| Sonnet 5 | $0.00000 | $0.00478 |
| Haiku 4.5 | $0.00000 | $0.00239 |
Grade A, and why
documentation-update-developer 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 3d 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 — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Documentation Update Guide
This prompt systematically updates developer-focused documentation to reflect current coding standards, development workflows, setup procedures, and technical implementation details.
🎯 OBJECTIVES:
- UPDATE coding standards to reflect current development practices
- SYNCHRONIZE setup procedures with current development environment
- MAINTAIN workflow documentation for current development processes
- ENSURE technical accuracy of implementation guides and examples
- VALIDATE development tool documentation and configurations
📋 DEVELOPER DOCUMENTATION UPDATE PROCESS:
STEP 1: Development Environment Assessment
Current Development Stack Analysis:
echo "💻 Development Environment Assessment"
echo "===================================="
# Check current technology versions
echo "Technology Stack Versions:"
node --version
npm --version
if [ -f "package.json" ]; then
echo "Package.json dependencies:"
cat package.json | grep -E "(next|react|typescript|vitest)" -A 1
fi
# Verify development tools
echo "Development Tools:"
ls -la .vscode/ .cursor/ 2>/dev/null || echo "No editor configs found"
# Check build and development scripts
echo "Available Scripts:"
if [ -f "package.json" ]; then
grep -A 10 '"scripts"' package.json
fi
# Verify environment configuration
echo "Environment Configuration:"
ls -la .env* 2>/dev/null || echo "No environment files found"
Development Workflow Changes:
- New development tools added to the development stack
- Updated dependencies affecting development workflow
- Changed build processes requiring documentation updates
- Modified testing strategies affecting developer workflow
- Updated deployment processes impacting development practices
Documentation Gap Analysis:
- Missing setup steps for new development tools
- Outdated configuration examples not reflecting current setup
- Incomplete workflow documentation missing recent processes
- Broken code examples that no longer work with current stack
- Missing troubleshooting guides for common development issues
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.
- 3d ago First seen · 333 lines · 0 tokens per session scan A a3d7a56f4d27
documentation-update-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 2,392 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
executing-red-team-engagement-planning
Red team engagement planning is the foundational phase that defines scope, objectives, rules of engagement (ROE), threat model selection, and operational timelines before any offensive testing begins.
omni-yaml-conventions
Omni Analytics model YAML conventions — file types, syntax patterns, field references, and common pitfalls. Apply when writing or editing Omni view, topic, or relationship YAML.
cypress-e2e-testing-cursorrules-prompt-file
Cursor rules for Cypress development with E2E testing.
deno-integration-techniques-cursorrules-prompt-fil
Cursor rules for Deno development with integration techniques.
cursorrules
Cursor rule "cursorrules" from Clarity-Digital-Twin/brain-go-brrr, covering .cursorrules - brain-go-brrr project (fixed architecture), rule #1: no parallel implementations ever, experiments/trainanything.py - must be thin, rule #2: check before building and rule #3: normalization is critical.
typescript-coding-style
description: Enforces code style and best practices for TypeScript files. globs: /.ts.