agentmods.dev

nextjs-best-practices

nextjs-best-practices is a skill for Claude Code, Codex from ivanshtokov/copilot-kit. It costs 22 tokens per session (928 once invoked), scanned A, a copy of nextjs-best-practices, MIT.

A reference guide for building applications with Next.js App Router, including server and browser components, data loading, and file-based routes.

In plain words
What is it for?
It is for designing routes, layouts, loading and error states, cached or live data fetching, forms, buttons, and other interactive pages.
Why use it?
It helps developers choose where code should run and how pages should load data and handle errors in a Next.js project.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 4repo 9mo ago A scan 22 tokens copy · 94% MIT

Good fit It is for designing routes, layouts, loading and error states, cached or live data fetching, forms, buttons, and other interactive pages.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ivanshtokov/copilot-kit/nextjs-best-practices
View source ↗ ivanshtokov/copilot-kit
Install

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.

Any agent
npx skills add ivanshtokov/copilot-kit --skill nextjs-best-practices
Clone the repo
git clone --depth 1 https://github.com/ivanshtokov/copilot-kit

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for nextjs-best-practices

README.md
[![agentmods](https://agentmods.dev/badge/skills/ivanshtokov/copilot-kit/nextjs-best-practices/github.svg)](https://agentmods.dev/skills/ivanshtokov/copilot-kit/nextjs-best-practices)
Your own site
<a href="https://agentmods.dev/skills/ivanshtokov/copilot-kit/nextjs-best-practices"><img src="https://agentmods.dev/badge/skills/ivanshtokov/copilot-kit/nextjs-best-practices/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.

agentmods 80×15 button for nextjs-best-practices

Your own site · 80×15
<a href="https://agentmods.dev/skills/ivanshtokov/copilot-kit/nextjs-best-practices"><img src="https://agentmods.dev/badge/skills/ivanshtokov/copilot-kit/nextjs-best-practices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 928 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 94% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00022 $0.00928
Opus 5.5 $0.00009 $0.00371
Sonnet 5.5 $0.00004 $0.00186
Haiku 4.5 $0.00002 $0.00093

Measured 2mo ago against content hash dc2588cf6a92, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

nextjs-best-practices 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 2mo 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.

Origin

This is a copy

94% identical to nextjs-best-practices — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.github/skills/nextjs-best-practices/SKILL.md · 203 lines

How it starts

The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Next.js Best Practices

Principles for Next.js App Router development.

1. Server vs Client Components

Decision Tree

Does it need...?
│
├── useState, useEffect, event handlers
│   └── Client Component ('use client')
│
├── Direct data fetching, no interactivity
│   └── Server Component (default)
│
└── Both? 
    └── Split: Server parent + Client child

By Default

Type Use
Server Data fetching, layout, static content
Client Forms, buttons, interactive UI

2. Data Fetching Patterns

Fetch Strategy

Pattern Use
Default Static (cached at build)
Revalidate ISR (time-based refresh)
No-store Dynamic (every request)

Data Flow

Source Pattern
Database Server Component fetch
API fetch with caching
User input Client state + server action

3. Routing Principles

File Conventions

File Purpose
page.tsx Route UI
layout.tsx Shared layout
loading.tsx Loading state
error.tsx Error boundary
not-found.tsx 404 page

Route Organization

Pattern Use
Route groups (name) Organize without URL
Parallel routes @slot Multiple same-level pages
Intercepting (.) Modal overlays

4. API Routes

Route Handlers

Method Use
GET Read data
POST Create data
PUT/PATCH Update data
DELETE Remove data

Best Practices

  • Validate input with Zod
  • Return proper status codes
  • Handle errors gracefully
  • Use Edge runtime when possible

5. Performance Principles

Image Optimization

  • Use next/image component
  • Set priority for above-fold
  • Provide blur placeholder
  • Use responsive sizes

Bundle Optimization

  • Dynamic imports for heavy components
  • Route-based code splitting (automatic)
  • Analyze with bundle analyzer

Read the full file on GitHub · 203 lines

Changes

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.

  1. 2mo ago First seen · 203 lines · 22 tokens per session scan A dc2588cf6a92

Subscribe to this mod's changes

nextjs-best-practices is a skill published in the GitHub repository ivanshtokov/copilot-kit (4 stars, last pushed 9mo ago), licensed MIT. It adds 22 tokens to every session and 928 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to nextjs-best-practices, differing in 1 line, and is treated as a copy.

FrontendReact
Related

nextjs-best-practices compared with skills from other repositories

nextjs-best-practices next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
nextjs-best-practicesivanshtokov/copilot-kitSkill49mo agoMITA22Claude Code, Codex
build-ghost-appTryGhost/GhostSkill56kyesterdayMITA44Claude Code, Codex
chakra-ui-builderchakra-ui/chakra-uiSkill41kyesterdayMITA214Claude Code, Codex
material-ui-tailwindmui/material-uiSkill99kyesterdayMITA67Claude Code, Codex
fuzzy-rankingTanStack/tableSkill29k4d agoMITA62Claude Code, Codex
r3f-best-practiceszebbern/claude-code-guideSkill4.7k3d agoMITA74Claude Code, Codex
git-safetytamagui/tamaguiSkill14ktodayMITA0Claude Code