Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/christopherlouet/claude-basenpx agentmods add skills/christopherlouet/claude-base/dev-nextjsWrote 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/christopherlouet/claude-base/dev-nextjs)<a href="https://agentmods.dev/skills/christopherlouet/claude-base/dev-nextjs"><img src="https://agentmods.dev/badge/skills/christopherlouet/claude-base/dev-nextjs/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/christopherlouet/claude-base/dev-nextjs"><img src="https://agentmods.dev/badge/skills/christopherlouet/claude-base/dev-nextjs.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.00050 | $0.02527 |
| Opus 5.5 | $0.00020 | $0.01011 |
| Sonnet 5.5 | $0.00010 | $0.00505 |
| Haiku 4.5 | $0.00005 | $0.00253 |
Grade A, and why
dev-nextjs scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const data = await fetch(url, { cache: "force-cache" }); How it starts
The opening of the file, as written. The whole thing — 320 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next.js App Router
App Router vs Pages Router
App Router (default since Next 13, stable): app/ folder, Server Components by default, Server Actions, streaming. Prefer for any new project.
Pages Router: pages/ folder, getServerSideProps/getStaticProps. Legacy, do not add new routes there.
If the project has both, coexist — both can live together, but do not duplicate a route.
Server Components by default
Any component in app/ is a Server Component by default. It runs on the server, zero client JS.
// app/posts/page.tsx — Server Component (default)
export default async function PostsPage() {
const posts = await db.posts.findMany(); // Direct SQL OK
return <PostList posts={posts} />;
}
Switch to Client Component with "use client"
// app/components/SearchBox.tsx
"use client"; // Directive at the top of the file
import { useState } from "react";
export function SearchBox() {
const [query, setQuery] = useState("");
return <input value={query} onChange={(e) => setQuery(e.target.value)} />;
}
Rule: "use client" only if you need hooks (useState, useEffect) or browser events (onClick, onChange). Otherwise, stay Server Component.
Server/Client composition
Server Components can import Client Components, but the reverse is not allowed (except via children props).
// OK: Server Component uses a Client Component
export default async function Page() {
const data = await fetch(...);
return <ClientChart data={data} />; // ClientChart is "use client"
}
// OK: Client Component receives a Server Component via children
"use client";
export function Layout({ children }: { children: React.ReactNode }) {
return <div>{children}</div>; // children can be a RSC
}
Data Fetching
Native fetch() with Next.js cache
// Forced cache (SSG-like, manual revalidation)
const data = await fetch(url, { cache: "force-cache" });
// No cache (SSR on every request)
const data = await fetch(url, { cache: "no-store" });
// Time-based revalidation (ISR)
const data = await fetch(url, { next: { revalidate: 60 } });
// Tag-based revalidation
const data = await fetch(url, { next: { tags: ["posts"] } });
// Then in a Server Action: revalidateTag("posts")
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 · +8 lines 0e0da88f8d9b
- 23d ago Changed · -2 lines 3c3f62a216af
- 24d ago Changed · -6 lines 676353d23a48
- 24d ago Changed · -1 lines 6945823f6efd
- 1mo ago First seen · 321 lines · 50 tokens per session scan A 5fa99cc62922
dev-nextjs is a skill published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 2d ago), licensed MIT. It adds 50 tokens to every session and 2,527 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
apollo-graphql
Guidelines for developing GraphQL APIs and React applications using Apollo Client for state management, data fetching, and caching.
agent-django-fastapi-expert
Specialist subagent: Django ORM, Django REST Framework, FastAPI async patterns, and Pydantic v2 specialist. Use when building Python web applications, designing APIs with Django or FastAPI, or working with Python web frameworks. Trigger phrases: Django, FastAPI, DRF, Django REST Framework, Pydantic, ORM, queryset…
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.
email-systems
Transactional email (Resend, SendGrid, SES), templates (React Email, MJML), deliverability (SPF/DKIM/DMARC), and inboxing best practices. Use when building email infrastructure, designing templates, or troubleshooting deliverability.
microservices-architecture
Microservices architecture patterns and best practices. Use when designing distributed systems, breaking down monoliths, or implementing service communication.
event-driven-architecture
Kafka, RabbitMQ, SQS/SNS, event sourcing, CQRS, saga patterns, dead letter queues, and idempotency. Use when designing asynchronous systems, implementing message-driven workflows, or building event streaming pipelines.