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 skills/inho-team/qe-mcp/qnextjs-developernpx skills add inho-team/qe-mcp --skill qnextjs-developergit clone --depth 1 https://github.com/inho-team/qe-mcpWrote 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/inho-team/qe-mcp/qnextjs-developer)<a href="https://agentmods.dev/skills/inho-team/qe-mcp/qnextjs-developer"><img src="https://agentmods.dev/badge/skills/inho-team/qe-mcp/qnextjs-developer.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.00139 | $0.01870 |
| Opus 5 | $0.00069 | $0.00935 |
| Sonnet 5 | $0.00028 | $0.00374 |
| Haiku 4.5 | $0.00014 | $0.00187 |
Grade A, and why
Qnextjs-developer 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 4d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next.js Developer
Senior Next.js developer with expertise in Next.js 16+ App Router, Server Components, Server Actions, Cache Components, Turbopack, and full-stack deployment with focus on performance, security, SEO, and agent-debuggable projects.
Current Version Notes (reviewed 2026-07-12)
- Verified current major: Next.js 16 (
npm view next version->16.2.10). - Official sources checked: Next.js 16, 16.2 AI improvements, 16.2 Turbopack, and the version 16 upgrade guide.
- Prefer App Router and Cache Components for new work. Treat Pages Router and legacy
getServerSideProps/getStaticPropsguidance as migration-only. - Next.js 16.2 adds agent-facing improvements and Turbopack work; still run
next buildbecause canary/backport behavior can differ from docs. - Security focus: validate server-side fetch targets, keep secrets server-only, and do not expose untrusted data through Server Actions or route handlers.
Core Workflow
- Architecture planning — Define app structure, routes, layouts, rendering strategy
- Implement routing — Create App Router structure with layouts, templates, loading/error states
- Data layer — Set up server components, data fetching, caching, revalidation
- Optimize — Images, fonts, bundles, streaming, edge runtime
- Deploy — Production build, environment setup, monitoring
- Validate: run
next buildlocally, confirm zero type errors, checkNEXT_PUBLIC_*and server-only env vars are set, run Lighthouse/PageSpeed to confirm Core Web Vitals > 90
- Validate: run
Reference Guide
Load detailed guidance based on context:
| Topic | Reference | Load When |
|---|---|---|
| App Router | references/app-router.md |
File-based routing, layouts, templates, route groups |
| Server Components | references/server-components.md |
RSC patterns, streaming, client boundaries |
| Server Actions | references/server-actions.md |
Form handling, mutations, revalidation |
| Data Fetching | references/data-fetching.md |
fetch, caching, ISR, on-demand revalidation |
| Deployment | references/deployment.md |
Vercel, self-hosting, Docker, optimization |
What ships with it
5 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.
- 4d ago First seen · 163 lines · 139 tokens per session scan A 629bdd66f77d
Qnextjs-developer is a skill published in the GitHub repository inho-team/qe-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 139 tokens to every session and 1,870 once invoked, about $0.0007 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-01.
Other skills, from other repositories
v8-jit
V8 JIT optimization patterns for writing high-performance JavaScript in Next.js server internals. Use when writing or reviewing hot-path code in app-render, stream-utils, routing, caching, or any per-request code path. Covers hidden classes / shapes, monomorphic call sites, inline caches, megamorphic deopt, closure…
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
verify
Use when you want to validate changes before committing, or when you need to check all React contribution requirements.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.
git-safety
Git safety rules. INVOKE WHEN: git push, force push, git reset, git clean, destructive git, push force, reset hard. NEVER force push or do destructive git operations.