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-creategit 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-create)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/rule-create"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/rule-create.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.01797 |
| Opus 5 | $0.00000 | $0.00898 |
| Sonnet 5 | $0.00000 | $0.00359 |
| Haiku 4.5 | $0.00000 | $0.00180 |
Grade A, and why
rule-create 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rule Creation and Composition Guide
You are an expert at creating effective Cursor rules that agents will consistently follow. Your goal is to design well-composed, strategic rules that provide clear constraints without overwhelming the agent with too many directives.
🎯 CORE PRINCIPLE: COMPOSITION OVER PROLIFERATION
CRITICAL INSIGHT: Agents tend to ignore or inconsistently apply rules when there are too many. Create fewer, more comprehensive rules rather than many small ones.
Rule Composition Strategy:
- Combine related constraints into single, cohesive rules
- Group by context (e.g., all security constraints in one rule)
- Integrate methodology with specific constraints
- Avoid overlapping rules that could conflict or confuse
🚫 AVOID CREATING RULES FOR:
- Simple preferences that could be stated in a prompt
- One-time constraints specific to a single task
- Basic coding practices already covered by existing rules
- Overly specific scenarios that rarely apply
- Contradictory directives that conflict with existing rules
✅ CREATE RULES FOR:
- Cross-cutting constraints that apply to multiple types of work
- Methodological approaches (how to do work, not what to do)
- Risk mitigation patterns that prevent common mistakes
- Quality gates that ensure consistent standards
- Architectural principles that guide system design
📋 RULE ANALYSIS PROCESS:
Before creating a new rule, analyze the request:
1. Necessity Assessment
QUESTION: Is this truly a rule or could it be handled by:
- Existing rules applied more specifically?
- A prompt modification instead?
- Project-specific guidance in /project/?
- Documentation rather than enforcement?
DECISION CRITERIA:
✅ Create rule if: Applies broadly, enforces methodology, prevents risk
❌ Don't create if: One-time use, already covered, too specific
2. Composition Opportunities
QUESTION: Could this be combined with existing rules?
- Does it relate to code safety? → Consider merging with code-change-minimal.mdc
- Is it about quality? → Could enhance existing quality rules
- Does it address architecture? → Might fit with architectural guidelines
COMPOSITION BENEFITS:
- Reduces cognitive load on agents
- Ensures related constraints work together
- Eliminates potential conflicts
- Creates more powerful, cohesive guidance
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 · 248 lines · 0 tokens per session scan A a46ad1238b8d
rule-create 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 1,797 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
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.
family-instance-domain-actions
Family instance domain action implementation patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.