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/prompt-update)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/prompt-update"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/prompt-update.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.02669 |
| Opus 5 | $0.00000 | $0.01334 |
| Sonnet 5 | $0.00000 | $0.00534 |
| Haiku 4.5 | $0.00000 | $0.00267 |
Grade A, and why
prompt-update 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 — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prompt Update and Maintenance Guide
This prompt provides a systematic approach to updating existing prompts, ensuring they remain current, standards-compliant, and effective while preserving their core value and functionality.
🎯 UPDATE OBJECTIVES:
- MAINTAIN prompt effectiveness while improving quality and compliance
- ALIGN with current standards and best practices
- PRESERVE core functionality and user familiarity
- ENHANCE user experience through targeted improvements
- ENSURE future maintainability and relevance
📋 PROMPT UPDATE PROCESS:
STEP 1: Current State Assessment
Prompt Analysis:
- Current version - Document existing version and last update date
- Usage patterns - How frequently is this prompt used and in what contexts?
- User feedback - Any reported issues, confusion, or enhancement requests
- Integration status - How well does it work with other prompts and rules?
- Standards compliance - Compare against current standards documents
Quality Baseline Measurement:
- Standards compliance score - Rate against docs/standards/standards-prompt.md
- Content quality score - Assess clarity, completeness, usability
- Technical accuracy - Verify information is current and correct
- User experience score - Evaluate ease of use and effectiveness
- Integration score - How well it works with current ecosystem
Change Requirements Identification:
- Standards gaps - What doesn't meet current standards?
- Outdated information - What technical details need updating?
- Missing functionality - What should be added to improve effectiveness?
- Usability issues - What causes confusion or poor user experience?
- Integration problems - Where does it conflict with other prompts/rules?
STEP 2: Update Planning
Scope Definition:
- Core preservation - What essential functionality must remain unchanged?
- Enhancement opportunities - What can be improved without breaking existing usage?
- Standards alignment - What specific standards compliance is needed?
- Version impact - Will this be a patch (x.x.1), minor (x.1.x), or major (1.x.x) update?
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 · 301 lines · 0 tokens per session scan A 2222be3e7c5a
prompt-update 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,669 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.