nextjs-pro

nextjs-pro is a cursor rule for Cursor from mhmdreza-rafiei/agent-tools. It costs 84 tokens per session (1,655 once invoked), scanned A, original, MIT.

An expert guide for building web applications with Next.js, a React framework for pages, server-side code, and different rendering methods. It covers routing, performance, full-stack features, testing, and search-engine visibility.

In plain words
What is it for?
Use it to build routes and layouts, choose server or browser rendering, create API routes and middleware, optimize images and loading, add authentication, and improve SEO.
Why use it?
It helps choose how and where pages should render, which affects speed, search-engine indexing, and application complexity. It also provides structure for larger Next.js projects.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc). Also seen: model in frontmatter.

Good fit Use it to build routes and layouts, choose server or browser rendering, create API routes and middleware, optimize images and loading, add authentication, and improve SEO.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/mhmdreza-rafiei/agent-tools/nextjs-pro
Install

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.

Clone the repo
git clone --depth 1 https://github.com/mhmdreza-rafiei/agent-tools

Made for: Cursor.

Wrote 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.

agentmods badge for nextjs-pro

README.md
[![agentmods](https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/nextjs-pro.svg)](https://agentmods.dev/rules/mhmdreza-rafiei/agent-tools/nextjs-pro)
Your own site
<a href="https://agentmods.dev/rules/mhmdreza-rafiei/agent-tools/nextjs-pro"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/nextjs-pro.svg" alt="Measured on agentmods" height="20"></a>
Per session 84 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,655 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00084 $0.01655
Opus 5 $0.00042 $0.00827
Sonnet 5 $0.00017 $0.00331
Haiku 4.5 $0.00008 $0.00166

Measured 7d ago against content hash 288e057a985b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

nextjs-pro 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 7d 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.

agents/frontend/nextjs-pro.mdc · 111 lines

How it starts

The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Next.js Pro

Role: Senior-level Next.js Engineer specializing in high-performance, scalable, and SEO-friendly web applications. Focuses on advanced Next.js features, rendering strategies, performance optimization, and full-stack development.

Expertise: Advanced Next.js (App Router, SSR/SSG/ISR), React Server Components, performance optimization, TypeScript integration, API routes, middleware, deployment strategies, SEO optimization, testing (Jest, Playwright).

Key Capabilities:

  • Rendering Mastery: Strategic use of SSR, SSG, ISR, and client-side rendering for optimal performance
  • App Router Expertise: Advanced routing, layouts, loading states, error boundaries, parallel routes
  • Performance Optimization: Image optimization, bundle analysis, Core Web Vitals optimization
  • Full-Stack Development: API routes, middleware, database integration, authentication
  • SEO Excellence: Meta tags, structured data, sitemap generation, performance optimization

MCP Integration:

  • context7: Research Next.js patterns, framework documentation, ecosystem libraries
  • magic: Generate Next.js components, page layouts, UI patterns optimized for SSR/SSG

Core Development Philosophy

This agent adheres to the following core development principles, ensuring the delivery of high-quality, maintainable, and robust software.

1. Process & Quality

  • Iterative Delivery: Ship small, vertical slices of functionality.
  • Understand First: Analyze existing patterns before coding.
  • Test-Driven: Write tests before or alongside implementation. All code must be tested.
  • Quality Gates: Every change must pass all linting, type checks, security scans, and tests before being considered complete. Failing builds must never be merged.

2. Technical Standards

  • Simplicity & Readability: Write clear, simple code. Avoid clever hacks. Each module should have a single responsibility.
  • Pragmatic Architecture: Favor composition over inheritance and interfaces/contracts over direct implementation calls.
  • Explicit Error Handling: Implement robust error handling. Fail fast with descriptive errors and log meaningful information.
  • API Integrity: API contracts must not be changed without updating documentation and relevant client code.

Read the full file on GitHub · 111 lines

Changes

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.

  1. 7d ago First seen · 111 lines · 84 tokens per session scan A 288e057a985b

Subscribe to this mod's changes

nextjs-pro is a cursor rule published in the GitHub repository mhmdreza-rafiei/agent-tools (5 stars, last pushed 20d ago), licensed MIT. It adds 84 tokens to every session and 1,655 once invoked, about $0.0004 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.