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 giuseppe-trisciuoglio/developer-kit --skill nextjs-code-reviewgit clone --depth 1 https://github.com/giuseppe-trisciuoglio/developer-kitWrote 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/giuseppe-trisciuoglio/developer-kit/nextjs-code-review)<a href="https://agentmods.dev/skills/giuseppe-trisciuoglio/developer-kit/nextjs-code-review"><img src="https://agentmods.dev/badge/skills/giuseppe-trisciuoglio/developer-kit/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/giuseppe-trisciuoglio/developer-kit/nextjs-code-review"><img src="https://agentmods.dev/badge/skills/giuseppe-trisciuoglio/developer-kit/nextjs-code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
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.00086 | $0.02287 |
| Opus 5.5 | $0.00034 | $0.00915 |
| Sonnet 5.5 | $0.00017 | $0.00457 |
| Haiku 4.5 | $0.00009 | $0.00229 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- nextjs-code-review — 97% identical, 8 lines differ
How it starts
The opening of the file, as written. The whole thing — 265 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.
- 1mo ago First seen · 265 lines · 86 tokens per session scan A 3267256fd633
nextjs-code-review is a skill published in the GitHub repository giuseppe-trisciuoglio/developer-kit (365 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 2,287 once invoked, about $0.0003 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-10.
Other skills, from other repositories
web-standards-reviewer
Review an existing web project for web-standards use and essential dependencies only, against the rules of /web-conventions, /javascript-conventions, and the stack skill the project composes (web-static, web-sprinkles, web-components), and answer with the shortest possible feedback — one line per finding, one line…
bce-reviewer
Review business component (BC) carving and Boundary-Control-Entity layering against the /bce rules and answer with the shortest possible feedback — one line per finding, one line when clean. Two modes, full for the whole codebase and diff for an incremental review of uncommitted changes or a git range. Stack-neutral…
argumentation
Construct well-structured arguments using the hypothesis-argument-example triad. Covers formulating falsifiable hypotheses, building logical arguments (deductive, inductive, analogical, evidential), providing concrete examples, and steelmanning counterarguments. Use when writing or reviewing PR descriptions that…
cross-review-project
Conduct a structured cross-project code review between two Claude Code instances via the cross-review-mcp broker. Each agent reads its own codebase, reviews the peer's code, and engages in evidence-backed dialogue — with QSG scaling laws enforcing review quality through minimum bandwidth constraints and phase-gated…
create-pull-request
Create and manage pull requests using GitHub CLI. Covers branch preparation, writing PR titles and descriptions, creating PRs, handling review feedback, and merge/cleanup workflows. Use when proposing changes from a feature or fix branch for review, merging completed work into the main branch, requesting code review…
review-pr
Forensic, stage-aware pull request review. Reconstructs the commit narrative, tests architectural premises against project reality, detects over-engineering, and produces a ready-to-post review comment. Use when the user says "review PR", "review this PR", "review PR #N", "is this PR ready to merge", "review the…