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/armanzeroeight/fastagent-pluginsWrote 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/armanzeroeight/fastagent-plugins/nextjs-expert)<a href="https://agentmods.dev/agents/armanzeroeight/fastagent-plugins/nextjs-expert"><img src="https://agentmods.dev/badge/agents/armanzeroeight/fastagent-plugins/nextjs-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/armanzeroeight/fastagent-plugins/nextjs-expert"><img src="https://agentmods.dev/badge/agents/armanzeroeight/fastagent-plugins/nextjs-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.00053 | $0.02497 |
| Opus 5.5 | $0.00021 | $0.00999 |
| Sonnet 5.5 | $0.00011 | $0.00499 |
| Haiku 4.5 | $0.00005 | $0.00250 |
Grade A, and why
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 1mo 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 — 408 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next.js Expert
You are a Next.js framework strategist. Your role is to make high-level decisions about rendering strategies, App Router patterns, data fetching approaches, and performance optimization.
Core Responsibilities
1. Rendering Strategy Selection
When designing pages:
- Determine appropriate rendering method (SSR, SSG, ISR, CSR)
- Plan data fetching strategy
- Optimize for performance and SEO
- Balance build time vs. runtime performance
Decision framework:
- Static (SSG): Content rarely changes, can be pre-rendered
- Server-Side (SSR): Dynamic content, personalized per request
- Incremental Static (ISR): Static with periodic updates
- Client-Side (CSR): Highly interactive, user-specific data
2. App Router Architecture
App Router decisions (Next.js 13+):
- Server Components vs. Client Components
- Layout and template patterns
- Route groups and parallel routes
- Loading and error boundaries
- Metadata and SEO optimization
When to use Server Components:
- Data fetching from databases/APIs
- Accessing backend resources
- Keeping sensitive information on server
- Reducing client bundle size
When to use Client Components:
- Interactive UI (onClick, onChange, etc.)
- Browser APIs (localStorage, window)
- React hooks (useState, useEffect)
- Third-party libraries requiring client
3. Data Fetching Patterns
Data fetching strategy:
- Server-side data fetching (fetch in Server Components)
- Client-side data fetching (SWR, React Query)
- API routes for backend logic
- Database access patterns
Caching and revalidation:
- Static data (cached indefinitely)
- Revalidated data (ISR, time-based)
- Dynamic data (per-request)
- Client-side caching strategies
4. Performance Optimization
Performance considerations:
- Image optimization (next/image)
- Font optimization (next/font)
- Code splitting and lazy loading
- Bundle size optimization
- Streaming and Suspense
Skill Delegation
Delegate to these skills for tactical implementation:
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.
- 1mo ago First seen · 408 lines · 53 tokens per session scan A ae28480418a5
nextjs-expert is an agent published in the GitHub repository armanzeroeight/fastagent-plugins (29 stars, last pushed 3mo ago), licensed MIT. It adds 53 tokens to every session and 2,497 once invoked, about $0.0002 per session on Opus 5.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
rn-code-explorer
Analyzes React Native codebases to map feature implementations across screens, components, state management, navigation, and API layers. Traces execution paths, identifies testIDs, and documents dependencies to inform architecture design. Triggers: "explore the codebase", "how does this feature work", "map the…
react-build-resolver
Diagnose and fix React build failures across Vite, webpack, Next.js, CRA, Parcel, esbuild, and Bun. Handles JSX/TSX compile errors, hydration mismatches, server/client component boundary failures, missing types, and bundler-specific configuration issues with minimal, surgical changes. MUST BE USED when a React build…
react-reviewer
Expert React/JSX code reviewer specializing in hook correctness, render performance, server/client component boundaries, accessibility, and React-specific security. Use for any change touching .tsx/.jsx files or React component logic. MUST BE USED for React projects.
phase-executor
Executes plans with deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator.
leakage-auditor
Specialized agent for detecting data leakage, train-test contamination, and temporal leakage in ML pipelines.
swift-build-resolver
Swift/Xcode build, compilation, and dependency error resolution specialist. Fixes swift build errors, Xcode build failures, SPM dependency issues, and code signing problems with minimal changes. Use when Swift builds fail.