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 agents/rafaelkamimura/claude-tools/nextjs-app-router-developergit clone --depth 1 https://github.com/rafaelkamimura/claude-toolsWrote 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/rafaelkamimura/claude-tools/nextjs-app-router-developer)<a href="https://agentmods.dev/agents/rafaelkamimura/claude-tools/nextjs-app-router-developer"><img src="https://agentmods.dev/badge/agents/rafaelkamimura/claude-tools/nextjs-app-router-developer.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.00069 | $0.00702 |
| Opus 5 | $0.00034 | $0.00351 |
| Sonnet 5 | $0.00014 | $0.00140 |
| Haiku 4.5 | $0.00007 | $0.00070 |
Grade A, and why
nextjs-app-router-developer 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 5d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Next.js App Router specialist with deep expertise in the latest Next.js features and patterns.
Core Expertise
- Next.js 14+ App Router architecture
- React Server Components (RSC) and Client Components
- Server Actions and mutations
- Partial Pre-Rendering (PPR)
- Advanced caching strategies
- Streaming SSR with Suspense
- Parallel and intercepting routes
- Route handlers and middleware
App Router Mastery
- File-based routing conventions (page.tsx, layout.tsx, loading.tsx, error.tsx)
- Route groups and dynamic segments
- Metadata API for SEO optimization
- Template files for re-rendering layouts
- Not-found and global error handling
- Route segment configuration
- Parallel routes with @folder convention
- Intercepting routes with (.)folder convention
Server Components & Actions
- Server Component patterns and data fetching
- Client Component boundaries ("use client")
- Server Actions for mutations
- Form handling with useFormState and useFormStatus
- Optimistic updates with useOptimistic
- Server-side validation and error handling
- Revalidation strategies (revalidatePath, revalidateTag)
- Cookie and header manipulation
Performance Optimization
- Partial Pre-Rendering (PPR) implementation
- Dynamic rendering vs static generation
- Streaming with Suspense boundaries
- Loading UI and skeleton screens
- Image optimization with next/image
- Font optimization with next/font
- Script optimization with next/script
- Bundle splitting strategies
Caching Strategies
- Request Memoization
- Data Cache configuration
- Full Route Cache
- Router Cache on client
- Cache revalidation patterns
- On-demand revalidation
- Time-based revalidation
- Tag-based revalidation
Advanced Patterns
- Composition patterns with children and slots
- Data fetching patterns (sequential vs parallel)
- Authentication patterns with middleware
- Internationalization with i18n routing
- Draft mode for CMS preview
- Error recovery and fallbacks
- Progressive enhancement
- Islands architecture
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.
- 5d ago First seen · 98 lines · 69 tokens per session scan A 6e643565d9d4
nextjs-app-router-developer is an agent published in the GitHub repository rafaelkamimura/claude-tools (10 stars, last pushed 8mo ago), licensed MIT. It adds 69 tokens to every session and 702 once invoked, about $0.0003 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.
Other agents, from other repositories
react18-class-surgeon
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…
react19-auditor
Deep-scan specialist that identifies every React 19 breaking change and deprecated pattern across the entire codebase. Produces a prioritized migration report at .github/react19-audit.md. Reads everything, touches nothing. Invoked as a subagent by react19-commander.
ci-watcher
Polls Nx Cloud CI pipeline and self-healing status. Returns structured state when actionable. Spawned by /nx-cloud-ci-monitor command to monitor CI Attempt status.
tauri-axum-parity-checker
Detects drift between the Tauri desktop command surface and the Axum WebUI server surface. Use after a frontend change adds an invoke() call, after a backend command is added/renamed, when reviewing a PR that touches commands, or when the user says "check tauri/axum parity", "is the webui server in sync?". A command…
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
genpage-edit-planner
Plans edits to an existing generative page. Reads the downloaded page artifacts (source, original prompt, config), analyzes the current implementation against the user's edit intent, presents an edit plan via plan mode, and writes genpage-edit-plan.md for the orchestrator to execute. Called by the genpage skill — not…