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-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-update-full)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/documentation-update-full"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/documentation-update-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.1 | $0.00000 | $0.02282 |
| Opus 5 | $0.00000 | $0.01141 |
| Sonnet 5 | $0.00000 | $0.00456 |
| Haiku 4.5 | $0.00000 | $0.00228 |
Grade A, and why
documentation-update-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 5d 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 — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Full Documentation Update Guide
This prompt orchestrates comprehensive updates across complete documentation suites, ensuring consistency, accuracy, and synchronization between architecture, developer, API, and user documentation.
🎯 OBJECTIVES:
- ORCHESTRATE multi-document updates across complete documentation suite
- ENSURE consistency between different documentation types
- SYNCHRONIZE information across architecture, developer, API, and user docs
- MAINTAIN quality standards across all documentation types
- COORDINATE version alignment between related documentation files
📋 FULL DOCUMENTATION UPDATE PROCESS:
STEP 1: Documentation Suite Analysis
Current Documentation Inventory:
echo "📚 Documentation Suite Analysis"
echo "==============================="
# Identify all documentation files
echo "Architecture Documentation:"
find docs/standards/ -name "*architecture*" -o -name "*design*"
echo "Developer Documentation:"
find docs/standards/ -name "*coding*" -o -name "*development*"
echo "API Documentation:"
find docs/standards/ -name "*api*" -o -name "openapi*"
echo "User Documentation:"
find docs/ -name "*user*" -o -name "*guide*" -o -name "README*"
# Check documentation consistency
echo "Documentation versions and dates:"
grep -r "lastUpdated\|version:" docs/ | head -10
Cross-Document Dependency Analysis:
- Shared concepts referenced across multiple documents
- Version dependencies between different documentation types
- Architecture decisions that affect multiple document types
- API changes that impact both developer and user documentation
- Technology updates affecting all documentation types
Update Scope Assessment:
- Changes since last update affecting multiple document types
- Consistency gaps between related documents
- Outdated cross-references between documents
- Version misalignment across documentation suite
- Missing information that should be synchronized
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.
- 5d ago First seen · 312 lines · 0 tokens per session scan A 50e635c6dfd6
documentation-update-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 2,282 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.