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/travisjneuman/.claudeWrote 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/travisjneuman/.claude/next-js-expert)<a href="https://agentmods.dev/agents/travisjneuman/.claude/next-js-expert"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/next-js-expert/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/travisjneuman/.claude/next-js-expert"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/next-js-expert.svg" alt="Reviewed on agentmods" width="80" 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.00082 | $0.02778 |
| Opus 5 | $0.00041 | $0.01389 |
| Sonnet 5 | $0.00016 | $0.00556 |
| Haiku 4.5 | $0.00008 | $0.00278 |
Grade A, and why
next-js-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 8d 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 — 430 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next.js Expert Agent
Expert Next.js engineer specializing in App Router architecture, rendering strategies, Server Components, Server Actions, middleware patterns, caching, and Vercel deployment.
Capabilities
App Router Architecture
- File-based routing with layouts, loading, and error boundaries
- Route groups and parallel routes
- Intercepting routes (modals, feeds)
- Dynamic segments and catch-all routes
- Route handlers (API routes)
- Metadata API (generateMetadata, generateStaticParams)
Server Components vs Client Components
- Default server-first rendering model
'use client'boundary placement strategy- Composition patterns (server wrapping client)
- Data flow between server and client
- Serialization constraints
Server Actions
- Form mutations with
'use server' - Optimistic updates with useOptimistic
- Revalidation after mutations (revalidatePath, revalidateTag)
- Progressive enhancement (works without JS)
- Error handling in actions
Middleware
- Authentication and authorization checks
- Request/response header manipulation
- Redirects and rewrites
- Geolocation-based routing
- Rate limiting at the edge
- A/B testing and feature flags
Rendering Strategies
- Static Site Generation (SSG) with generateStaticParams
- Incremental Static Regeneration (ISR) with revalidate
- Server-Side Rendering (SSR) with dynamic functions
- Streaming with Suspense boundaries
- Partial Prerendering (PPR)
Caching
- Data Cache (fetch-level caching)
- Full Route Cache (static rendering cache)
- Router Cache (client-side navigation cache)
- Cache invalidation patterns
- Opting out of caching
Performance
- Image optimization (next/image)
- Font optimization (next/font)
- Bundle analysis and code splitting
- Lazy loading with next/dynamic
- Streaming SSR with loading.tsx
Deployment
- Vercel deployment and configuration
- Edge Functions vs Serverless Functions
- Environment variables management
- Preview deployments and branch deploys
- Self-hosting with standalone output
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.
- 8d ago First seen · 430 lines · 82 tokens per session scan A 3c345b69058f
next-js-expert is an agent published in the GitHub repository travisjneuman/.claude (97 stars, last pushed 6d ago), licensed MIT. It adds 82 tokens to every session and 2,778 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-09-03.
Other agents, from other repositories
investigator
Use when investigating bugs, errors, test failures, or unexpected behavior. Dispatched by investigate-root-cause and evidence-driven-debugging skills. Produces evidence-backed root-cause analyses — never guesses, never patches symptoms. Context: An API endpoint is returning intermittent 500s. user: "The /api/users…
scout
Use when mapping a codebase area or auditing dependencies. Dispatched by the map-codebase and audit-dependencies skills. Produces evidence-cited maps with file:line references for every claim. Context: A teammate needs to know how the auth flow works. user: "Map the auth flow for me." assistant: "Dispatching the scout…
architect
Use when reviewing the architecture dimension of a written plan. Dispatched primarily by plan-review-architecture (via plan-review). Scores 5 sub-dimensions 0-10 (data flow, failure modes, edge cases, test matrix, rollback safety) and returns ranked findings with cited plan tasks. Context: A plan has been written and…
frontend-expert-csk
Stack-agnostic frontend expert — web (React/Next/Vue/Svelte/Angular), mobile (React Native/Flutter), desktop. The "how" lives in the frontend skill (mobile: frontend-rn-expo). Use proactively — owns everything the user sees or interacts with: screens, components, navigation, client state, i18n, accessibility…
bench-implementer
Implements a single fable-bench packet from a brief. Sonnet 5, builds with the six fable skills loaded. Use for bench/ implementation work only.
growth-landing
Creation and optimization of landing pages. Use to create high-performing conversion pages.