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/armanzeroeight/fastagent-plugins/nextjs-expertgit 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.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.00053 | $0.02497 |
| Opus 5 | $0.00026 | $0.01248 |
| Sonnet 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 yesterday.
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.
- yesterday 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 1mo ago), licensed MIT. It adds 53 tokens to every session and 2,497 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-09-03.
Other agents, from other repositories
Zhin Frontend Optimizer
Use when improving Zhin.js console pages, plugin frontend pages, React UI structure, page information architecture, responsiveness, rendering performance, and visual hierarchy. 适用于前端页面优化、控制台界面改进、React 交互与布局优化。.
react-coder
Use this agent when you need to create or modify React components following the project's simplicity-first philosophy. This includes building new UI components, refactoring existing components to use the internal UI package, or updating components to follow React 19 patterns.
react-architect
Use this agent when you need expert guidance on React application architecture, component design, performance optimization, or code quality improvements. This agent is specifically tuned for this project's tech stack (Tauri v2, React 19, shadcn/ui v4, Tailwind v4, Zustand v5, Vitest v3) and should be used for…
CHANGELOG
本文档记录 Zhin.js 项目 GitHub Copilot Agent 的更新历史。.
plugin-developer
Use when building or modifying Zhin.js plugins, including plugin entry files, command handlers, middleware, Context registration and injection, schema, service extraction, and plugin-side web integrations. 适用于插件开发、命令实现、中间件编写和 Context 接入。.
zhin
Use when implementing or modifying Zhin.js framework code, especially framework features, cross-package changes, plugin runtime integration, command handling, Context APIs, and end-to-end code changes that must follow repository conventions. 适用于 Zhin.js 框架开发、跨包实现和符合仓库约定的代码落地。.