nextjs-seo-performance

nextjs-seo-performance is a skill for Claude Code from t-code4change/nextjs-claude-skills. It costs 94 tokens per session (5,495 once invoked), scanned A, original, MIT.

A set of checks and implementation guidance for improving search visibility and loading speed in Next.js websites. Next.js is a framework for building web applications with JavaScript and React.

In plain words
What is it for?
Use it to audit metadata, social sharing data, structured data, sitemaps, robots rules, images, fonts, scripts, bundles, and Core Web Vitals.
Why use it?
It helps find problems that can keep pages out of search results or make them slow for visitors.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is { path: '../fonts/custom-400.woff2', weight: '400', style: 'normal' },.

Good fit Use it to audit metadata, social sharing data, structured data, sitemaps, robots rules, images, fonts, scripts, bundles, and Core Web Vitals.

Compare 6 skills from other repositories ↓
Install

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.

Clone the repo
git clone --depth 1 https://github.com/t-code4change/nextjs-claude-skills
agentmods
npx agentmods add skills/t-code4change/nextjs-claude-skills/nextjs-seo-performance

Made for: Claude Code.

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-seo-performance

README.md
[![agentmods](https://agentmods.dev/badge/skills/t-code4change/nextjs-claude-skills/nextjs-seo-performance/github.svg)](https://agentmods.dev/skills/t-code4change/nextjs-claude-skills/nextjs-seo-performance)
Your own site
<a href="https://agentmods.dev/skills/t-code4change/nextjs-claude-skills/nextjs-seo-performance"><img src="https://agentmods.dev/badge/skills/t-code4change/nextjs-claude-skills/nextjs-seo-performance/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-seo-performance

Your own site · 80×15
<a href="https://agentmods.dev/skills/t-code4change/nextjs-claude-skills/nextjs-seo-performance"><img src="https://agentmods.dev/badge/skills/t-code4change/nextjs-claude-skills/nextjs-seo-performance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 94 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,495 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found 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.00094 $0.05495
Opus 5.5 $0.00038 $0.02198
Sonnet 5.5 $0.00019 $0.01099
Haiku 4.5 $0.00009 $0.00549

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

Security

Grade A, and why

nextjs-seo-performance 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 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl https://your-site.com/robots.txt
nextjs-seo-performance/SKILL.md · 763 lines

How it starts

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

Next.js SEO & Performance

Priority: SEO correctness → Core Web Vitals → Bundle size → Runtime perf. A fast page that isn't indexed is worthless. An indexed page that's slow loses rankings.


Quick SEO Audit

curl https://your-site.com/robots.txt
curl https://your-site.com/sitemap.xml
curl -s https://your-site.com | grep -E '<title|<meta name="description|og:image|og:title'
curl -s https://your-site.com | grep 'application/ld+json'
# Core Web Vitals (field data): https://pagespeed.web.dev
# Lighthouse is lab-only — CANNOT measure INP (most failed metric)

1. Metadata API

Root Layout

// app/layout.tsx
import type { Metadata, Viewport } from 'next';

// viewport MUST be a separate export — not inside metadata object
export const viewport: Viewport = {
  width: 'device-width',
  initialScale: 1,
  maximumScale: 5,
  themeColor: [
    { media: '(prefers-color-scheme: light)', color: '#ffffff' },
    { media: '(prefers-color-scheme: dark)', color: '#0a0a0a' },
  ],
};

export const metadata: Metadata = {
  metadataBase: new URL(process.env.NEXT_PUBLIC_SITE_URL ?? 'https://your-site.com'),
  title: {
    default: 'Site Name — Main Keyword',
    template: '%s | Site Name',
  },
  description: 'Compelling 150–160 char description with primary keyword.',
  openGraph: {
    type: 'website',
    locale: 'en_US',
    siteName: 'Site Name',
    images: [{ url: '/og-image.png', width: 1200, height: 630, alt: 'Site preview' }],
  },
  twitter: { card: 'summary_large_image', images: ['/og-image.png'] },
  alternates: { canonical: '/' },
  robots: {
    index: true,
    follow: true,
    googleBot: { index: true, follow: true, 'max-image-preview': 'large' },
  },
};

Dynamic Metadata (per page)

// app/products/[slug]/page.tsx
type Props = { params: Promise<{ slug: string }> };  // Promise in Next.js 15+

export async function generateMetadata({ params }: Props): Promise<Metadata> {
  const { slug } = await params;
  const product = await getProduct(slug);
  if (!product) return { title: 'Not Found' };
  return {
    title: product.name,               // template in layout applies automatically
    description: product.description.slice(0, 160),
    openGraph: {
      title: product.name,
      images: [{ url: product.image, width: 1200, height: 630, alt: product.name }],
    },
    alternates: { canonical: `/products/${slug}` },
  };
}

Read the full file on GitHub · 763 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 · 763 lines · 94 tokens per session scan A d7e2f7114577

Subscribe to this mod's changes

nextjs-seo-performance is a skill published in the GitHub repository t-code4change/nextjs-claude-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 94 tokens to every session and 5,495 once invoked, about $0.0004 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-08-31.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens