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/rizkyhaksono/portfolio-v3/nextjs-developmentgit clone --depth 1 https://github.com/rizkyhaksono/portfolio-v3Wrote 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/rizkyhaksono/portfolio-v3/nextjs-development)<a href="https://agentmods.dev/rules/rizkyhaksono/portfolio-v3/nextjs-development"><img src="https://agentmods.dev/badge/rules/rizkyhaksono/portfolio-v3/nextjs-development.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.05302 | $0.05302 |
| Opus 5 | $0.02651 | $0.02651 |
| Sonnet 5 | $0.01060 | $0.01060 |
| Haiku 4.5 | $0.00530 | $0.00530 |
Grade A, and why
nextjs-development 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.
This is a copy
97% identical to nextjs-development — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 806 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next.js Development Rules
You are an expert full-stack TypeScript engineer working with Next.js. Produce production-ready code that follows modern Next.js App Router patterns and best practices.
Tech Stack Guidelines
- Next.js 15+ (App Router) + React 19
- TypeScript (strict mode)
- Testing: Vitest + React Testing Library + MSW
- Styling: Tailwind CSS + shadcn/ui (when applicable)
- Package Manager: npm
- UI layout: See
.cursor/rules/ui-layout-consistency.mdc— solid / glass / inset surfaces only; usePageBody,PageSection,Surface,MacWindow,SectionHeading
Focus on: separation of concerns, strict typing, accessibility, performance, and comprehensive testing.
Project Structure
src/
├─ app/ # App Router (RSC by default)
│ ├─ _components/ # App-level (RSC-ok) components
│ ├─ api/ # API routes for external webhooks only
│ ├─ (routes)/ # Route groups and pages
│ └─ layout.tsx
├─ components/ # Reusable client/RSC components
│ ├─ ui/ # Base UI components
│ └─ [feature]/ # Feature-specific components
├─ lib/ # Utilities and shared helpers
├─ server/ # Server-side code
│ ├─ api/ # tRPC API layer
│ │ ├─ routers/ # tRPC router composition
│ │ ├─ procedures/ # Individual tRPC procedures
│ │ ├─ root.ts # Root router
│ │ └─ trpc.ts # tRPC setup
│ ├─ services/ # Business logic services
│ └─ clients/ # External service clients
├─ db/ # Database schema & migrations
├─ tools/ # AI tool definitions
├─ prompts/ # AI prompt templates
└─ trpc/ # tRPC client setup
test/
├─ unit/ # Unit tests
├─ integ/ # Integration tests
└─ e2e/ # End-to-end tests
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 · 806 lines · 5,302 tokens per session scan A ef720b0ddf2c
nextjs-development is a cursor rule published in the GitHub repository rizkyhaksono/portfolio-v3 (6 stars, last pushed 5d ago), licensed MIT. It adds 5,302 tokens to every session, about $0.0265 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to nextjs-development, differing in 4 lines, and is treated as a copy.
Other cursor rules, from other repositories
development-conventions
Development conventions, code style, and best practices for the Kaneo project.
general
Wonder Blocks design system conventions, component patterns, and coding standards.
new-component
Workflow for creating new React components.
trove-react
React 19 coding conventions and performance patterns. Auto-activates when working with React/TypeScript files. Covers hooks, state management, TanStack Query, Zustand, immutable updates, and component conventions.
component-patterns
React Component Patterns.
hydration-safety
React hydration mismatch prevention.