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 s0vers/next-app-i18n-starter --skill nextjs-seo-measurementgit clone --depth 1 https://github.com/s0vers/next-app-i18n-starterWrote 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/s0vers/next-app-i18n-starter/nextjs-seo-measurement)<a href="https://agentmods.dev/skills/s0vers/next-app-i18n-starter/nextjs-seo-measurement"><img src="https://agentmods.dev/badge/skills/s0vers/next-app-i18n-starter/nextjs-seo-measurement/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/s0vers/next-app-i18n-starter/nextjs-seo-measurement"><img src="https://agentmods.dev/badge/skills/s0vers/next-app-i18n-starter/nextjs-seo-measurement.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.00090 | $0.00962 |
| Opus 5.5 | $0.00036 | $0.00385 |
| Sonnet 5.5 | $0.00018 | $0.00192 |
| Haiku 4.5 | $0.00009 | $0.00096 |
Grade A, and why
nextjs-seo-measurement 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 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.
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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Measuring SEO on Next.js
Each platform reports its own observation. Search Console shows how Google served the site, GA4 shows what visitors did. Neither confirms the other, and neither proves a change worked until a stated window passes.
Read
| Task | Reference |
|---|---|
| Which tool answers which question, setup for a multilingual site, metric traps, diagnosing a traffic drop, one locale's drop, a silent locale | Measurement |
Diagnose the drop here, then hand the failing layer to the skill that owns the fix.
Rules
- Ask what "traffic" means (clicks, sessions, users, revenue) before reading any number. The metrics differ by design. [doc]
- Never add Search Console clicks to GA4 sessions. They count different events. [doc]
- Compare like with like: same date range, same country and device filters, same page set, and the same days of the week. Otherwise a change in the filter reads as a change in traffic. [practice]
- A locale with no impressions is an indexing or targeting problem first. Check the gate for one of its URLs before touching content. [practice]
- Check whether an anomaly matches a known Google update or an outage on the platform's status page before blaming the site. An update or outage moves many sites at once. [practice]
Working method
- Orient. Read the root
AGENTS.mdif the project has one, the route and its rendered output, and the file that builds page metadata. Never read.env. Done when you can name that file. - Frame. Write the URL set, page type, locale or market, and target outcome, one line each. Ask only when an answer changes the work, and state the default you will use if nobody answers. Done when all four lines exist and every open question is asked or carries a stated default.
- Change and verify. Make the smallest change with the project's own helpers. When a server is running and the
nextjs-seo-technicalskill is installed, run itsscripts/verify-seo.mjs(in this starter:bun run seo:verify), then the project's lint and build. Done when every check ends in one of the four verdicts below. - Report, in the shape below.
What ships with it
2 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.
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 First seen · 44 lines · 90 tokens per session scan A a4003be3f286
nextjs-seo-measurement is a skill published in the GitHub repository s0vers/next-app-i18n-starter (66 stars, last pushed 6d ago), licensed MIT. It adds 90 tokens to every session and 962 once invoked, about $0.0004 per session on Opus 5.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-09-30.
Other skills, from other repositories
ultracite
Ultracite is a zero-config linting and formatting preset for JavaScript/TypeScript projects. Use when: (1) Setting up or initializing Ultracite in a project (ultracite init), (2) Running linting or formatting commands (check, fix, doctor), (3) Writing or reviewing JS/TS code in a project that uses Ultracite — to…
next-upgrade
Upgrade Next.js to the latest version following official migration guides and codemods.
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance…
vercel-react-view-transitions
Guide for implementing smooth, native-feeling animations using React's View Transition API ( component, addTransitionType, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components…
next-cache-components
Next.js 16 Cache Components - PPR, use cache directive, cacheLife, cacheTag, updateTag.