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/farzannajipour/cursor-react-rules/nextjs-app-routergit clone --depth 1 https://github.com/Farzannajipour/cursor-react-rulesWrote 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/farzannajipour/cursor-react-rules/nextjs-app-router)<a href="https://agentmods.dev/rules/farzannajipour/cursor-react-rules/nextjs-app-router"><img src="https://agentmods.dev/badge/rules/farzannajipour/cursor-react-rules/nextjs-app-router.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.01200 | $0.01200 |
| Opus 5 | $0.00600 | $0.00600 |
| Sonnet 5 | $0.00240 | $0.00240 |
| Haiku 4.5 | $0.00120 | $0.00120 |
Grade A, and why
nextjs-app-router 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 3d 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next.js 14+ with App Router, TypeScript, and Tailwind CSS
You are an expert Next.js developer specializing in the App Router, Server Components, and modern React patterns.
Tech Stack
- Next.js 14+ (App Router)
- React 18+ (Server Components)
- TypeScript 5+
- Tailwind CSS
- Server Actions
- Prisma (database ORM)
- NextAuth.js (authentication)
Core Principles
Server Components by Default
- All components in app/ are Server Components by default
- Only add 'use client' when you need:
- useState, useEffect, or other React hooks
- Event handlers (onClick, onChange, etc.)
- Browser APIs (window, localStorage, etc.)
- Third-party libraries that use client features
Example Pattern:
// ✅ Server Component (default) - NO 'use client'
export default async function UserProfile({ userId }: { userId: string }) {
const user = await db.user.findUnique({ where: { id: userId } });
return (
<div>
<h1>{user.name}</h1>
<UserActions user={user} /> {/* Client Component */}
</div>
);
}
// ✅ Client Component (only when needed)
'use client';
export function UserActions({ user }: { user: User }) {
const [isFollowing, setIsFollowing] = useState(user.isFollowing);
return (
<button onClick={() => setIsFollowing(!isFollowing)}>
{isFollowing ? 'Unfollow' : 'Follow'}
</button>
);
}
Data Fetching
Server Components (Preferred):
// app/users/[id]/page.tsx
export default async function UserPage({ params }: { params: { id: string } }) {
// Fetch directly in component
const user = await db.user.findUnique({
where: { id: params.id },
include: { posts: true }
});
if (!user) notFound();
return <UserProfile user={user} />;
}
// Enable ISR
export const revalidate = 3600; // Revalidate every hour
Server Actions (Mutations)
// lib/actions/user.ts
'use server';
import { revalidatePath } from 'next/cache';
import { db } from '@/lib/db';
export async function updateUserProfile(userId: string, data: ProfileData) {
const user = await db.user.update({
where: { id: userId },
data: {
name: data.name,
bio: data.bio,
},
});
// Revalidate affected pages
revalidatePath(`/users/${userId}`);
return { success: true, user };
}
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.
- 3d ago First seen · 215 lines · 1,200 tokens per session scan A 3955e48ce0ed
nextjs-app-router is a cursor rule published in the GitHub repository Farzannajipour/cursor-react-rules (3 stars, last pushed 7mo ago), licensed MIT. It adds 1,200 tokens to every session, about $0.0060 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-31.
Other cursor rules, from other repositories
css-styling
CSS architecture, tokens, and styling rules for this Docusaurus site. Apply when creating or modifying components, styles, layouts, or any UI-facing code.
general
Wonder Blocks design system conventions, component patterns, and coding standards.
frontend-web
Cursor rule "frontend-web" from groupultra/telegram-search, covering frontend (apps/web), routing, layouts & navigation, state & data fetching, ui, styling & ux and error handling & notifications.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.