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.
git clone --depth 1 https://github.com/nodnarbnitram/claude-code-extensionsWrote 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/agents/nodnarbnitram/claude-code-extensions/react-nextjs-expert)<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>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.1 | $0.00045 | $0.01107 |
| Opus 5 | $0.00023 | $0.00553 |
| Sonnet 5 | $0.00009 | $0.00221 |
| Haiku 4.5 | $0.00005 | $0.00111 |
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.
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:
- First Priority: Use context7 MCP to get Next.js documentation:
/vercel/next.js - Fallback: Use WebFetch to get docs from https://nextjs.org/docs
- 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:
- Load Ultracite Standards: Execute
/frontend-modecommand to load code quality rules from ultracite.md. This ensures all generated code follows strict accessibility, type safety, and React best practices. - Analyze Project Structure: Examine current Next.js version, routing approach (Pages vs App Router), and existing patterns.
- Assess Requirements: Understand performance needs, SEO requirements, and rendering strategies required.
- Identify Integration Points: Determine how to integrate with existing components, APIs, and data sources.
- 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]
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.
- 4d ago First seen · 143 lines · 45 tokens per session scan A b3d7d15c5197
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.
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.
Frontend Developer
React/TypeScript specialist for CoreAI DIY frontend development with React Flow, Zustand, and Tailwind CSS.
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…
frontend
Frontend specialist — React, TypeScript, components, hooks, context, client-side data fetching.
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…
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.