Borrowing it
Nothing to install: this file belongs to bryanweaver/claude-agent-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bryanweaver/claude-agent-kit/main/.claude/skills/nextjs-app-router/SKILL.mdgit clone --depth 1 https://github.com/bryanweaver/claude-agent-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/bryanweaver/claude-agent-kit/nextjs-app-router)<a href="https://agentmods.dev/skills/bryanweaver/claude-agent-kit/nextjs-app-router"><img src="https://agentmods.dev/badge/skills/bryanweaver/claude-agent-kit/nextjs-app-router.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.1 | $0.00050 | $0.02136 |
| Opus 5 | $0.00025 | $0.01068 |
| Sonnet 5 | $0.00010 | $0.00427 |
| Haiku 4.5 | $0.00005 | $0.00214 |
Grade A, and why
nextjs-app-router 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 8d 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 — 390 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next.js App Router Patterns
Modern patterns for Next.js 14+ with the App Router.
Server vs Client Components
Decision Guide
Use Server Components (default) when:
- Fetching data
- Accessing backend resources directly
- Keeping sensitive information on server (API keys, tokens)
- Large dependencies that shouldn't increase client bundle
- No interactivity needed
Use Client Components ('use client') when:
- Using React hooks (useState, useEffect, useContext)
- Adding event listeners (onClick, onChange)
- Using browser-only APIs
- Using custom hooks that depend on state/effects
- Using React Class components
Server Component (default)
// app/users/page.tsx
// No directive needed - Server Component by default
import { createClient } from '@/lib/supabase/server';
export default async function UsersPage() {
const supabase = createClient();
const { data: users } = await supabase.from('users').select('*');
return (
<div>
<h1>Users</h1>
<ul>
{users?.map(user => (
<li key={user.id}>{user.name}</li>
))}
</ul>
</div>
);
}
Client Component
'use client';
import { useState } from 'react';
export default function Counter() {
const [count, setCount] = useState(0);
return (
<button onClick={() => setCount(count + 1)}>
Count: {count}
</button>
);
}
Composition Pattern (Server + Client)
// app/dashboard/page.tsx (Server Component)
import { createClient } from '@/lib/supabase/server';
import { DashboardClient } from './DashboardClient';
export default async function DashboardPage() {
const supabase = createClient();
const { data: stats } = await supabase.from('stats').select('*');
// Pass server data to client component
return <DashboardClient initialStats={stats} />;
}
// app/dashboard/DashboardClient.tsx (Client Component)
'use client';
import { useState } from 'react';
export function DashboardClient({ initialStats }) {
const [stats, setStats] = useState(initialStats);
// Interactive logic here
}
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.
- 8d ago First seen · 390 lines · 50 tokens per session scan A 489411b6a4a6
nextjs-app-router is a skill published in the GitHub repository bryanweaver/claude-agent-kit (2 stars, last pushed 2mo ago), licensed MIT. It adds 50 tokens to every session and 2,136 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-08-31.
Other skills, from other repositories
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
menu-transitions-rtl
Animate react-horizontal-scrolling-menu scrolling and build right-to-left menus: noPolyfill defaults to true since v8, so transitionDuration (default 500), a custom-easing-function transitionBehavior, and per-call ScrollOptions { duration, boundary } on scrollToItem/scrollNext/scrollPrev are silently ignored unless…