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 biggora/claude-plugins-registry --skill next-best-practicesgit clone --depth 1 https://github.com/biggora/claude-plugins-registryWrote 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/biggora/claude-plugins-registry/next-best-practices)<a href="https://agentmods.dev/skills/biggora/claude-plugins-registry/next-best-practices"><img src="https://agentmods.dev/badge/skills/biggora/claude-plugins-registry/next-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.
<a href="https://agentmods.dev/skills/biggora/claude-plugins-registry/next-best-practices"><img src="https://agentmods.dev/badge/skills/biggora/claude-plugins-registry/next-best-practices.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.00077 | $0.01372 |
| Opus 5 | $0.00039 | $0.00686 |
| Sonnet 5 | $0.00015 | $0.00274 |
| Haiku 4.5 | $0.00008 | $0.00137 |
Grade A, and why
next-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 9d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next.js Best Practices
Use the project's installed Next.js version as the source of truth. This skill is baselined against the latest stable documentation for Next.js 16.3.3, but project-local, version-matched docs take precedence.
Start With the Project's Mode
Before proposing code:
- Read
package.json, the lockfile,next.config.*, and the relevantapp/orpages/files. - If present, follow the Next.js-managed block in the repository's
AGENTS.mdand read the matching docs innode_modules/next/dist/docs/. - Confirm whether
cacheComponentsandpartialPrefetchingare enabled. They materially change caching, prerendering, and<Link>behavior. - Preserve the existing router. Do not migrate from Pages Router to App Router unless the task requests it.
- Treat canary and
experimental.*features as opt-in. Do not enable them merely because they exist in the latest docs.
For version detection, bundled docs, Turbopack defaults, and the stable-versus-experimental boundary in 16.3, read version-and-tooling.
Cache Components Mode Gate
| Mode | Correct model |
|---|---|
cacheComponents absent or false |
Existing route segment options such as dynamic, revalidate, and fetchCache remain valid. Apply the project's version-matched caching docs. |
cacheComponents: true |
Data is dynamic by default. Use <Suspense> for request-time work and 'use cache' plus cacheLife/cacheTag for cached work. Remove dynamic, revalidate, and fetchCache; they fail config validation in this mode. Cache Components requires the Node.js runtime. |
cacheComponents: true, partialPrefetching: true |
Each route gets a reusable App Shell. URL-specific work using params or searchParams belongs behind <Suspense> unless a link intentionally prefetches it. Audit existing <Link prefetch={true}> calls before adopting. |
Read cache-components before changing caching mode and core-navigation before changing prefetch behavior.
What ships with it
14 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.
- references/api-components.mdx 5.5 KB
- references/cache-components.mdx 6.1 KB
- references/caching-revalidation.mdx 5.8 KB
- references/core-navigation.mdx 5.0 KB
- references/core-routing.mdx 3.7 KB
- references/core-server-client-components.mdx 4.7 KB
- references/data-fetching-client.mdx 5.1 KB
- references/data-fetching-server.mdx 5.1 KB
- references/data-streaming.mdx 4.6 KB
- references/file-conventions-dynamic-routes.mdx 6.1 KB
- references/file-conventions-loading-error.mdx 3.6 KB
- references/metadata-seo.mdx 5.8 KB
- references/server-actions.mdx 7.6 KB
- references/version-and-tooling.mdx 4.1 KB
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.
- 9d ago First seen · 74 lines · 77 tokens per session scan A 646646f17113
next-best-practices is a skill published in the GitHub repository biggora/claude-plugins-registry (2 stars, last pushed 11d ago), licensed MIT. It adds 77 tokens to every session and 1,372 once invoked, about $0.0004 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…