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 ccplugins/awesome-claude-code-plugins --skill nextjs-appgit clone --depth 1 https://github.com/ccplugins/awesome-claude-code-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/skills/ccplugins/awesome-claude-code-plugins/nextjs-app)<a href="https://agentmods.dev/skills/ccplugins/awesome-claude-code-plugins/nextjs-app"><img src="https://agentmods.dev/badge/skills/ccplugins/awesome-claude-code-plugins/nextjs-app/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/ccplugins/awesome-claude-code-plugins/nextjs-app"><img src="https://agentmods.dev/badge/skills/ccplugins/awesome-claude-code-plugins/nextjs-app.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector 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.00105 | $0.01063 |
| Opus 5.5 | $0.00042 | $0.00425 |
| Sonnet 5.5 | $0.00021 | $0.00213 |
| Haiku 4.5 | $0.00011 | $0.00106 |
Grade A, and why
nextjs-app 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
nextjs-app
Bootstrap a new Next.js web app the way this owner builds them: App Router, TypeScript strict, current stable packages, no deprecated APIs, a clean feature structure, and the house git and CI workflow.
First read these shared rules (they override anything you remember):
../shared/house-rules.md, ../shared/no-ai-attribution.md,
../shared/git-and-ci.md, ../shared/docs-and-context.md,
../shared/hardening.md, and (for public repos) ../shared/open-source-docs.md.
Step 0. Get the brief, then ask the variant questions (hard stop)
This is a hard stop. Do not run any scaffolding command until the user has answered.
First, get the project brief: one paragraph on what the app does, its main features, target users, and any hard constraints. If the user has not given one, ask for it. The brief drives naming, the route groups, and the data model.
Then present the variant choices below, wait for the answers, and build. If a choice has multiple options, ask; do not assume. Ask in one batch.
- Repo visibility: private, open-source (public), or private-plus-open-source
(a private product with a separate public core or SDK). See
references/variants.md. - Data layer: Prisma + Postgres (default), a different DB, or none yet.
- Auth: next-auth v5 (default), Clerk, or none yet.
- UI kit: shadcn/ui + Tailwind (default), Mantine, or plain Tailwind.
- Deploy target: Vercel (default) or self-host (Docker).
- Package manager: pnpm (default) or npm.
If the user already answered some of these in their prompt, do not re-ask.
Step 1. Verify environment and current versions
- Check Node (
node -v, want the current LTS or newer) and the package manager. - Run
scripts/check-latest.shto get live stable versions from npm. Pin those, not versions from memory. See../shared/house-rules.mdrule 2. - Pull current Next.js docs before writing framework code
(
../shared/docs-and-context.md). Recent Next.js ships docs innode_modules/next/dist/docs/; read the relevant guide and obey deprecation notices.
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.
- 1mo ago First seen · 89 lines · 105 tokens per session scan A 8989b000f743
nextjs-app is a skill published in the GitHub repository ccplugins/awesome-claude-code-plugins (974 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 105 tokens to every session and 1,063 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…