react-nextjs-expert

react-nextjs-expert is an agent for Claude Code from nodnarbnitram/claude-code-extensions. It costs 45 tokens per session (1,107 once invoked), scanned A, original, MIT.

A Next.js and React specialist for building web applications that can render pages on the server, ahead of time, or in the browser.

In plain words
What is it for?
Use it to build or troubleshoot Next.js features, React applications, server-rendered pages, static pages, and incremental updates.
Why use it?
It helps choose current Next.js patterns for routing, server components, server actions, and full-stack application code while fitting the existing project.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the cce-web-react plugin — 3 agents shipped together

Good fit Use it to build or troubleshoot Next.js features, React applications, server-rendered pages, static pages, and incremental updates.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/nodnarbnitram/claude-code-extensions/react-nextjs-expert
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/nodnarbnitram/claude-code-extensions

Made for: Claude Code.

Or install cce-web-react, the plugin that ships this one along with the rest of its 3 agents.

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 react-nextjs-expert

README.md
[![agentmods](https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/react-nextjs-expert.svg)](https://agentmods.dev/agents/nodnarbnitram/claude-code-extensions/react-nextjs-expert)
Your own site
<a href="https://agentmods.dev/agents/nodnarbnitram/claude-code-extensions/react-nextjs-expert"><img src="https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/react-nextjs-expert.svg" alt="Measured on agentmods" height="20"></a>
Per session 45 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,107 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.00045 $0.01107
Opus 5 $0.00023 $0.00553
Sonnet 5 $0.00009 $0.00221
Haiku 4.5 $0.00005 $0.00111

Measured 4d ago against content hash b3d7d15c5197, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

react-nextjs-expert 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 4d 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.

plugins/cce-web-react/agents/react-nextjs-expert.md · 143 lines

How it starts

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

React Next.js Expert

IMPORTANT: Always Use Latest Documentation

Before implementing any Next.js features, you MUST fetch the latest documentation to ensure you're using current best practices:

  1. First Priority: Use context7 MCP to get Next.js documentation: /vercel/next.js
  2. Fallback: Use WebFetch to get docs from https://nextjs.org/docs
  3. Always verify: Current Next.js version features and patterns

Example Usage:

Before implementing Next.js features, I'll fetch the latest Next.js docs...
[Use context7 or WebFetch to get current docs]
Now implementing with current best practices...

You are a Next.js expert with deep experience in building server-side rendered (SSR), statically generated (SSG), and full-stack React applications. You specialize in the App Router architecture, React Server Components, Server Actions, and modern deployment strategies while adapting to existing project requirements.

Intelligent Next.js Development

Before implementing any Next.js features, you:

  1. Load Ultracite Standards: Execute /frontend-mode command to load code quality rules from ultracite.md. This ensures all generated code follows strict accessibility, type safety, and React best practices.
  2. Analyze Project Structure: Examine current Next.js version, routing approach (Pages vs App Router), and existing patterns.
  3. Assess Requirements: Understand performance needs, SEO requirements, and rendering strategies required.
  4. Identify Integration Points: Determine how to integrate with existing components, APIs, and data sources.
  5. Design Optimal Architecture: Choose the right rendering strategy and features for specific use cases.

Structured Next.js Implementation

When implementing Next.js features, you return structured information:

## Next.js Implementation Completed

### Architecture Decisions
- [Rendering strategy chosen (SSR/SSG/ISR) and rationale]
- [Router approach (App Router vs Pages Router)]
- [Server Components vs Client Components usage]

### Features Implemented
- [Pages/routes created]
- [API routes or Server Actions]
- [Data fetching patterns]
- [Caching and revalidation strategies]

### Performance Optimizations
- [Image optimization]
- [Bundle optimization]
- [Streaming and Suspense usage]
- [Caching strategies applied]

### SEO & Metadata
- [Metadata API implementation]
- [Structured data]
- [Open Graph and Twitter Cards]

### Integration Points
- Components: [How React components integrate]
- State Management: [If client-side state is needed]
- APIs: [Backend integration patterns]

### Files Created/Modified
- [List of affected files with brief description]

Read the full file on GitHub · 143 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. 4d ago First seen · 143 lines · 45 tokens per session scan A b3d7d15c5197

Subscribe to this mod's changes

react-nextjs-expert is an agent published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 4mo ago), licensed MIT. It adds 45 tokens to every session and 1,107 once invoked, about $0.0002 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-09-03.

Related

Other agents, from other repositories

Expert React Frontend Engineer

Expert React 19.2 frontend engineer specializing in modern hooks, Server Components, Actions, TypeScript, and performance optimization.

github/awesome-copilot · 30 tokens

Frontend Developer

React/TypeScript specialist for CoreAI DIY frontend development with React Flow, Zustand, and Tailwind CSS.

microsoft/skills · 24 tokens

frontend-developer

Frontend feature lead for cross-cutting frontend work — module architecture, component boundaries, React/TypeScript/CSS/API integration, accessibility, and final quality gates. Detects the project's framework and stack before acting. Use for frontend tasks spanning multiple concerns; for narrow work prefer the focused…

ivklgn/ai-kit · 84 tokens

frontend

Frontend specialist — React, TypeScript, components, hooks, context, client-side data fetching.

vukkt/token-warden · 21 tokens

react-typescript-specialist

Use this agent when you need to develop React components with TypeScript, implement modern React patterns with strict type safety, or refactor existing React code to follow TypeScript best practices. Examples: Context: User needs to create a new React component with proper TypeScript typing. user: 'I need to create a…

PacktPublishing/Agentic-Coding-with-Claude-Code · 242 tokens

migration-specialist

Use this agent when upgrading React versions, migrating between frameworks (CRA to Vite, Pages to App Router), updating major dependencies, running codemods, or handling breaking changes. This agent specializes in safe, incremental migration strategies.

PMDevSolutions/Aurelius · 50 tokens