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 skills add sutchan/Agent-Skills-Hub --skill nextjs-code-reviewgit clone --depth 1 https://github.com/sutchan/Agent-Skills-HubWrote 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/skills/sutchan/agent-skills-hub/nextjs-code-review)<a href="https://agentmods.dev/skills/sutchan/agent-skills-hub/nextjs-code-review"><img src="https://agentmods.dev/badge/skills/sutchan/agent-skills-hub/nextjs-code-review/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/skills/sutchan/agent-skills-hub/nextjs-code-review"><img src="https://agentmods.dev/badge/skills/sutchan/agent-skills-hub/nextjs-code-review.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.00072 | $0.02385 |
| Opus 5.5 | $0.00029 | $0.00954 |
| Sonnet 5.5 | $0.00014 | $0.00477 |
| Haiku 4.5 | $0.00007 | $0.00238 |
Grade A, and why
nextjs-code-review 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 16d 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.
This is a copy
97% identical to nextjs-code-review — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next.js Code Review
Overview
Evaluates Next.js App Router code against best practices for Server Components, Client Components, Server Actions, caching strategies, and production-readiness criteria. Produces actionable findings categorized by severity with concrete code examples. Delegates to typescript-software-architect-review agent for architectural analysis.
When to Use
- Reviewing Next.js pages, layouts, and route segments before merging
- Validating Server Component vs Client Component boundaries
- Checking Server Actions for security and correctness
- Reviewing data fetching patterns (fetch, cache, revalidation)
- Evaluating caching strategies (static generation, ISR, dynamic rendering)
- Assessing middleware implementations (authentication, redirects, rewrites)
- Reviewing API route handlers for proper request/response handling
- Validating metadata configuration for SEO
- Checking loading, error, and not-found page implementations
- After implementing new Next.js features or migrating from Pages Router
Instructions
-
Identify Scope: Determine which Next.js route segments and components are under review. Use
globto discoverpage.tsx,layout.tsx,loading.tsx,error.tsx,route.ts, andmiddleware.tsfiles. -
Analyze Component Boundaries: Verify proper Server Component / Client Component separation. Check that
'use client'is placed only where necessary and as deep in the component tree as possible. Ensure Server Components don't import client-only modules. -
Review Data Fetching: Validate fetch patterns — check for proper
cacheandrevalidateoptions, parallel data fetching withPromise.all, and avoidance of request waterfalls. Verify that server-side data fetching doesn't expose sensitive data to the client. -
Evaluate Caching Strategy: Review static vs dynamic rendering decisions. Check
generateStaticParamsusage for static generation,revalidatePath/revalidateTagfor on-demand revalidation, and proper cache headers for API routes.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 16d ago Changed 837c298835a3
- 22d ago Changed a424175ff89b
- 1mo ago First seen · 269 lines · 72 tokens per session scan A 8b17d91bd1f5
nextjs-code-review is a skill published in the GitHub repository sutchan/Agent-Skills-Hub (2 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 2,385 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to nextjs-code-review, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
前端代码审查
A review checklist for browser-based front-end and React code. It covers security, accessibility, speed, React correctness, maintainability, and Forsion’s no-build environment rules.
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
react-code-review
Provides comprehensive code review capability for React applications, validates component architecture, hooks usage, React 19 patterns, state management, performance optimization, accessibility compliance, and TypeScript integration. Use when reviewing React code changes, before merging pull requests, after…
react-hook-form-audit
Audit existing React Hook Form code for correctness, accessibility, validation, data ownership, submission, dirty-state, field-array, wizard, controlled-widget, and performance problems. Use when reviewing RHF forms, investigating form bugs or rerenders, or checking an RHF-heavy change. Read-only; use react-hook-form…
react
React component architecture and data-flow guidance for composition, state ownership, Effects, Suspense, async UI, rendering behavior, and measured performance. Use when building, recommending, or auditing React component APIs, hooks, providers, transitions, rerenders, or server/client component boundaries. Route…