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/squirrelogic/cursor-rules/nextjs-15git clone --depth 1 https://github.com/squirrelogic/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.00000 | $0.01149 |
| Opus 5 | $0.00000 | $0.00575 |
| Sonnet 5 | $0.00000 | $0.00230 |
| Haiku 4.5 | $0.00000 | $0.00115 |
Grade A, and why
nextjs-15 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 2d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next.js 15 Best Practices
actions:
Folder Structure Rules
-
type: reject conditions:
- pattern: "^src/" message: "Avoid using a src folder; structure your project as per Next.js 15 conventions."
-
type: suggest message: | Ensure your Next.js 15 project follows this directory structure:
app/ ├── actions/ # Server actions ├── api/ # API routes ├── auth/ # Authentication related pages ├── login/ # Login page └── signup/ # Signup page components/ ├── auth/ # Authentication components ├── layout/ # Layout components └── ui/ # UI components (shadcn) db/ └── schema/ # Drizzle schema files lib/ # Libraries and utilities public/ # Static assets utils/ # Utility functions
General Best Practices
- type: reject
conditions:
-
pattern: "import\s+.\s+from\s+['"]../." message: "Use absolute imports instead of relative imports. Configure paths in tsconfig.json"
-
pattern: "use client['"]\s*;?\s*export\s+default\s+function\s+Page" message: "page.tsx files should not include 'use client'; they are server-only by default"
-
pattern: "export\s+default\s+function\s+Page\s*(\s*{\sparams\s}\s*)\s*{" message: "Pages with params or searchParams should be async functions"
-
pattern: "<img\s+src=" message: "Use Next.js Image component for optimized images"
-
Form Handling
- type: suggest
conditions:
- pattern: "<form"
message: |
Form best practices:
- Use react-hook-form for form handling
- Use Zod for form validation
- Handle form errors appropriately
- Submit to server actions Example:
'use client'; import { useForm } from "react-hook-form"; import { zodResolver } from "@hookform/resolvers/zod"; import { z } from "zod"; const schema = z.object({ // your schema }); export default function Form() { const form = useForm({ resolver: zodResolver(schema) }); return ( <form action={async (formData) => { // server action }}> {/* form fields */} </form> ); }
- pattern: "<form"
message: |
Form best practices:
Layout Rules
-
type: reject conditions:
- pattern: "export\s+default\s+function\s+\w+Layout\s*(\s*{\schildren\s,\sparams\s}\s*)\s*{" message: "Layouts with params should be async functions"
-
type: suggest conditions:
- pattern: "function\s+\w+Layout"
message: |
Layout best practices:
- RootLayout should be a standard function
- Layouts with params should be async
- Implement loading.tsx for Suspense
- Implement not-found.tsx for 404 errors
- pattern: "function\s+\w+Layout"
message: |
Layout best practices:
Route Handler Rules
-
type: reject conditions:
- pattern: "export\s+function\s+(GET|POST|PUT|DELETE|PATCH)\s*(" message: "Route handlers should be async functions"
-
type: suggest conditions:
- pattern: "route.ts$"
message: |
Route handler best practices:
import { NextResponse } from 'next/server'; export async function GET( request: Request, { params }: { params: { id: string } } ) { try { // Your logic here return NextResponse.json({ data }); } catch (error) { return NextResponse.json( { error: 'Error message' }, { status: 500 } ); } }
- pattern: "route.ts$"
message: |
Route handler best practices:
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.
- 2d ago First seen · 173 lines · 1,149 tokens per session scan A ecfd8affbb01
nextjs-15 is a cursor rule published in the GitHub repository squirrelogic/cursor-rules (20 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,149 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-30.
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.