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/kabi10/cursor-rules/nextjs-patternsgit clone --depth 1 https://github.com/Kabi10/cursor-rulesWhat 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.00456 | $0.00456 |
| Opus 5 | $0.00228 | $0.00228 |
| Sonnet 5 | $0.00091 | $0.00091 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
nextjs-patterns 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 yesterday.
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.
What it actually says
Next.js Patterns
🔄 Component Patterns
-
Server Components (Default)
// ✅ Correct: Default to Server Components export default async function Page({ params }) { const data = await getData(); return <Component data={data} />; } -
Client Components (When Needed)
// ✅ Correct: Mark as client when needed 'use client'; export function InteractiveComponent() { const [state, setState] = useState(); return <div onClick={() => setState(!state)}>{state}</div>; }
📡 Data Fetching
-
Server-Side Data Fetching
// ✅ Correct: Fetch in Server Components async function getData() { const res = await fetch('https://api.example.com/data', { next: { revalidate: 3600 } }); return res.json(); } -
Error Handling
// ✅ Correct: Use error.tsx export default function Error({ error, reset, }: { error: Error; reset: () => void; }) { return ( <div> <h2>Something went wrong!</h2> <button onClick={() => reset()}>Try again</button> </div> ); }
Examples
Critical Rules
- Default to Server Components
- Use 'use client' only when necessary
- Implement proper error boundaries
- Include loading states
- Follow Next.js file conventions
- Use metadata API for SEO description: globs: alwaysApply: false
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.
- yesterday First seen · 87 lines · 456 tokens per session scan A 81db16eda369
nextjs-patterns is a cursor rule published in the GitHub repository Kabi10/cursor-rules (21 stars, last pushed 2mo ago), licensed MIT. It adds 456 tokens to every session, about $0.0023 per session on Opus 5. 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-30.
Other cursor rules, from other repositories
project-rules
Cursor rule "project-rules" from peva3/anchor, covering cursor ai rules, core directives, critical enforcements, pre-commit checklist and required folders.
general
Cursor rule "general" from maxgfr/conforme, covering claude.md, project overview, build & test, architecture and keeping docs in sync.
cursor-project-rule
Project Spine operating contract for "Ledger API".
project-spine-apps-web
Project Spine scoped guidance for "apps/web".
project-spine-packages-ui
Project Spine scoped guidance for "packages/ui".
adapter-consistency
adapter-consistency.