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/omergulcicek/omergulcicek.com/nextjsgit clone --depth 1 https://github.com/omergulcicek/omergulcicek.comWrote 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/omergulcicek/omergulcicek.com/nextjs)<a href="https://agentmods.dev/rules/omergulcicek/omergulcicek.com/nextjs"><img src="https://agentmods.dev/badge/rules/omergulcicek/omergulcicek.com/nextjs.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.00817 |
| Opus 5 | $0.00000 | $0.00409 |
| Sonnet 5 | $0.00000 | $0.00163 |
| Haiku 4.5 | $0.00000 | $0.00082 |
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 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next.js 16 App Router Constitution
Constraints
- Server-First Architecture: All components in
src/appMUST be Server Components (RSC) by default. - Client Component Usage: The
"use client"directive is strictly limited to leaf-node components that require interactivity (hooks, events) or Browser APIs. - Feature Delegation:
src/appis strictly for routing/layout. All business logic, UI components, and domain hooks MUST reside insrc/features. - Server Actions: All mutations MUST use Server Actions defined in dedicated
actions.tsfiles withinsrc/features. Actions MUST call the API layer only; direct database access inside actions is forbidden. - i18n Implementation: Use
next-intlfor translations. Follow the patterns defined ini18n.mdc. - Metadata: SEO metadata MUST be defined using the Metadata API in
page.tsxorlayout.tsx. - Streaming: Use
loading.tsxfor route-level async states. Use<Suspense>for granular feature-level hydration. - CSRF Protection: Verify Origin/Referer headers in Server Actions. Use
action.bindto lock sensitive IDs on the server-side. - Secret Isolation: Use the
server-onlypackage in API and database files to prevent accidental leakage to the client.
Bans
- Inline Server Actions: Defining Server Actions inside components or pages is FORBIDDEN.
- Client-Side Data Fetching in Effects: Using
useEffectfor data fetching is FORBIDDEN. Use TanStack Query or RSC. - Logic in Route Files: Implementing complex logic directly in
page.tsxorlayout.tsxis FORBIDDEN. - Manual Head Management: Using
head.tsxor manual<meta>tags is FORBIDDEN. - "use client" at Root: Marking
page.tsxorlayout.tsxas"use client"is FORBIDDEN. Wrap interactive logic in feature components instead. - Raw Serialization: Forbidden to pass raw database models or sensitive user data directly from RSC to Client Components.
Correct Implementation
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 · 91 lines · 0 tokens per session scan A 80abb9326dd3
nextjs is a cursor rule published in the GitHub repository omergulcicek/omergulcicek.com (15 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 817 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-09-01.
Other cursor rules, from other repositories
frontend-development
Most coagents examples have a ui/ folder with Next.js applications.
examples-and-demos
Multi-agent systems with complex workflows.
suggestions-development
When working with suggesitons, always load this up.
agent-development
Python agents are typically in folders named agent-py/ or agent/ and use the sdk-python/ package.
development-workflow
CopilotKit uses a monorepo structure with.
quick-reference
Cursor rule "quick-reference" from CopilotKit/CopilotKit, covering copilotkit quick reference, need to...?, build a simple copilot, create multi-agent systems and integrate with crewai.