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/rule-updategit 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/rule-update)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/rule-update"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/rule-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.02658 |
| Opus 5 | $0.00000 | $0.01329 |
| Sonnet 5 | $0.00000 | $0.00532 |
| Haiku 4.5 | $0.00000 | $0.00266 |
Grade A, and why
rule-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 6d 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 — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rule Update and Maintenance Guide
This prompt provides a systematic approach to updating existing Cursor rules, ensuring they remain strategically composed, standards-compliant, and effective while preserving their core value and preventing rule proliferation.
🎯 UPDATE OBJECTIVES:
- MAINTAIN rule effectiveness while improving strategic composition
- ALIGN with current standards and composition principles
- PRESERVE core constraints and user familiarity
- ENHANCE strategic cohesion through better rule composition
- PREVENT rule proliferation by identifying consolidation opportunities
📋 RULE UPDATE PROCESS:
STEP 1: Current State Assessment
Rule Analysis:
- Current version - Document existing version and last update date
- Usage patterns - How frequently is this rule applied and in what contexts?
- Effectiveness metrics - Is the rule consistently followed by agents?
- Integration status - How well does it work with other rules and prompts?
- Standards compliance - Compare against current rule standards and composition principles
Strategic Composition Assessment:
- Rule overlap analysis - Does this rule conflict or overlap with other rules?
- Composition opportunities - Could this be merged with related rules for better cohesion?
- Agent adherence rate - Do agents consistently apply this rule or ignore it?
- Scope clarity - Is the rule's scope well-defined and appropriate?
- Constraint effectiveness - Do the constraints actually improve outcomes?
Quality Baseline Measurement:
- Standards compliance score - Rate against docs/standards/standards-rule.md
- Strategic alignment score - How well does it fit the composition-over-proliferation principle?
- Clarity and actionability - Can agents easily understand and apply the rule?
- Integration score - How well it works with the current rule ecosystem
- Effectiveness score - Does it prevent issues and improve outcomes?
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.
- 6d ago First seen · 289 lines · 0 tokens per session scan A 714efccbb996
rule-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,658 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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.