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 instructions/t-code4change/nextjs-claude-skills/agents-mdgit clone --depth 1 https://github.com/t-code4change/nextjs-claude-skillsWrote 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/instructions/t-code4change/nextjs-claude-skills/agents-md)<a href="https://agentmods.dev/instructions/t-code4change/nextjs-claude-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/t-code4change/nextjs-claude-skills/agents-md.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.00665 | $0.00665 |
| Opus 5 | $0.00332 | $0.00332 |
| Sonnet 5 | $0.00133 | $0.00133 |
| Haiku 4.5 | $0.00067 | $0.00067 |
Grade A, and why
nextjs-claude-skills AGENTS.md 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next.js Best Practices — AI Agent Rules
This file is automatically read by Codex and OpenAI-compatible agents. Source: https://github.com/t-code4change/nextjs-claude-skills
CRITICAL: Server vs Client Components
- Default to Server Components — no
'use client'unless component needs useState/useEffect/browser APIs - Place
'use client'at leaf components only (smallest boundary) - Never import Server Components into Client Components — pass as
childreninstead - Props from Server to Client must be serializable
CRITICAL: Data Fetching
- Fetch data in Server Components — never useEffect for data fetching
- Use
Promise.all()for parallel fetches — never sequential awaits - Server Actions are for MUTATIONS ONLY — never use for data fetching
- Next.js 15+: always
await params,await cookies(),await headers()
SEO — Always Apply
- Every page needs: unique
<title>,<meta description>, canonical URL metadataBasemust be set in root layoutviewportmust be a separate export — never insidemetadataobject- Use
generateMetadata()for dynamic routes - Never use CSR (
useEffectfetch) for SEO-indexed content - Never block
/_next/in robots.txt - Set canonical URL on every indexable page to prevent duplicate content
- Add JSON-LD structured data on key pages
Images
- Always use
next/image— never<img>tag - LCP image must have
priorityprop - All images need explicit
width/heightorfillwith sized container - Set
sizesattribute to match actual rendered dimensions - Use
quality={85}for hero images, default 75 for others
Fonts
- Always use
next/font— never Google Fonts<link>or@import - Always set
display: 'swap'
Scripts / Analytics
- Load analytics with
strategy="afterInteractive"vianext/script - Use
@next/third-parties/googlefor GA4
Bundle
- Import directly from file, not from barrel index files
- Use
dynamic()for heavy components that aren't needed on first load
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 · 75 lines · 665 tokens per session scan A e151506fcd99
nextjs-claude-skills AGENTS.md is an instructions file published in the GitHub repository t-code4change/nextjs-claude-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 665 tokens to every session, about $0.0033 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 instructions, from other repositories
semiotic CLAUDE.md
Claude Code instructions for nteract/semiotic, covering semiotic claude code instructions and claude code notes.
ai AGENTS.md
AGENTS.md instructions for vercel/ai, covering agents.md, project overview, repository structure, key directories and core package dependencies.
pip-web CLAUDE.md
Claude Code instructions for playpip/pip-web, covering claude.md — agent guide for pip, read first (by task), the three layers (respect the boundaries), non-negotiables and commands / definition of done.
rush AGENTS.md
Instructions for onurhan1337/rush, covering project rules for ikas app starter app (next.js), core principles, stack overview, mcp usage and graphql and api workflow.
tanstack-start-template AGENTS.md
AGENTS.md instructions for dyeoman2/tanstack-start-template, covering tanstack start agent guide, core philosophy, architecture, golden rules and key patterns.
next-sanity CLAUDE.md
Claude Code instructions for sanity-io/next-sanity, a project described as: Sanity toolkit for Next.js.