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/t-code4change/nextjs-claude-skillsWrote 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/t-code4change/nextjs-claude-skills/nextjs)<a href="https://agentmods.dev/rules/t-code4change/nextjs-claude-skills/nextjs"><img src="https://agentmods.dev/badge/rules/t-code4change/nextjs-claude-skills/nextjs/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/t-code4change/nextjs-claude-skills/nextjs"><img src="https://agentmods.dev/badge/rules/t-code4change/nextjs-claude-skills/nextjs.svg" alt="Reviewed on agentmods" width="80" 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.00535 | $0.00535 |
| Opus 5.5 | $0.00214 | $0.00214 |
| Sonnet 5.5 | $0.00107 | $0.00107 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade A, and why
nextjs 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 2mo 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.
What it actually says
Next.js Best Practices
Server vs Client Components
- Default to Server Components. Add
'use client'only for useState/useEffect/browser APIs - Place
'use client'at leaf level (smallest boundary possible) - Never import Server Components into Client Components — pass as
children
Data Fetching
- Fetch in Server Components, not useEffect
- Use
Promise.all()for parallel independent fetches - Server Actions = mutations only, never data fetching
- Next.js 15+: await params, cookies(), headers()
SEO — Every Page
metadataBasein root layout (required for relative OG URLs)viewportas separate export — NOT inside metadata objectgenerateMetadata()for dynamic routes- Canonical URL on every indexable page
- JSON-LD structured data on key pages (Organization, Product, Article, FAQ)
- Never block
/_next/in robots.txt
Images (next/image only)
priorityon the LCP image (hero/above-fold)- Explicit
width/heightORfill+ sized container — prevents CLS sizesattribute matching actual rendered widthquality={85}for hero images
Fonts (next/font only)
- Never Google Fonts
<link>tags or CSS@import - Always
display: 'swap'
Scripts
next/scriptwithstrategy="afterInteractive"for analytics- Use
@next/third-parties/googlefor GA4
Bundle
- Direct imports — never barrel/index file imports in Client Components
dynamic(() => import('./Heavy'))for non-critical heavy components
Caching (Next.js 16)
'use cache'= first statement, function must be async- Always pair: cacheTag() + cacheLife()
- No cookies()/headers() inside 'use cache'
- updateTag() in Server Actions after mutations
- Wrap dynamic content in
Core Web Vitals
- LCP < 2.5s: priority on hero image, fast TTFB, next/font
- INP < 200ms: useTransition, useDeferredValue, no blocking event handlers
- CLS < 0.1: image dimensions, font swap, min-height for async content
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.
- 2mo ago First seen · 57 lines · 535 tokens per session scan A 21b23ab4b095
nextjs is a cursor rule published in the GitHub repository t-code4change/nextjs-claude-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 535 tokens to every session, about $0.0021 per session on Opus 5.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-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.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).