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 textura-agency/next16-claude-starter --skill i18n-seogit clone --depth 1 https://github.com/textura-agency/next16-claude-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/textura-agency/next16-claude-starter/i18n-seo)<a href="https://agentmods.dev/skills/textura-agency/next16-claude-starter/i18n-seo"><img src="https://agentmods.dev/badge/skills/textura-agency/next16-claude-starter/i18n-seo/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/textura-agency/next16-claude-starter/i18n-seo"><img src="https://agentmods.dev/badge/skills/textura-agency/next16-claude-starter/i18n-seo.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.00165 | $0.03369 |
| Opus 5.5 | $0.00066 | $0.01348 |
| Sonnet 5.5 | $0.00033 | $0.00674 |
| Haiku 4.5 | $0.00016 | $0.00337 |
Grade A, and why
i18n-seo 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 3d 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.
language: `curl -s -A "Googlebot/2.1" <url>/de | grep x-robot-view`. How it starts
The opening of the file, as written. The whole thing — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-language SEO
Google indexes each language version as its own page. hreflang only tells it which version to show whom — it never merges or ranks them. So each version needs its own URL, its own complete server-rendered HTML in that language, and links between the versions that agree.
Read before touching code: node_modules/next/dist/docs/01-app/02-guides/internationalization.md
(Next 16: app/[lang], next/root-params), and src/proxy.ts +
obsidian/frontend/robot-form.md (the robot form).
1. Decide the structure (ask the client)
| Structure | Example | Use when |
|---|---|---|
| Subdirectories (recommended) | acme.com/de/… |
almost always — one domain's authority, one deploy, one Search Console property |
| ccTLDs | acme.de |
separate businesses per country, local trust matters more than shared authority; a deploy/domain per market |
| Subdomains | de.acme.com |
only when infrastructure forces it — authority splits like ccTLDs without their local signal |
?lang=de / cookie / Accept-Language on one URL |
— | never — one URL serves one language to Google |
Language or language + market? de serves every German reader; de-AT /
de-CH only when the content really differs (prices, legal, spelling).
Don't create region variants with identical text.
2. Routes — the language comes from the URL
Hard rule #15 still holds: routes stay static, nothing reads headers() /
cookies(). The language is a route segment.
src/app/[lang]/layout.tsx ← the root layout: <html lang={lang}>
src/app/[lang]/page.tsx ← imports only from src/views (rule #5)
src/app/[lang]/about/page.tsx
src/app/[lang]/robot-view/page.tsx
src/app/sitemap.ts, robots.ts, llms.txt/, api/ ← stay outside [lang]
(With Payload: src/app/(site)/[lang]/… beside (payload).)
// src/app/[lang]/layout.tsx
import { notFound } from "next/navigation";
import { LOCALES, hasLocale } from "@/lib/i18n";
export const generateStaticParams = () => LOCALES.map((lang) => ({ lang }));
export const dynamicParams = false; // an unknown language is a 404, not a render
export default async function RootLayout({ children, params }: LayoutProps<"/[lang]">) {
const { lang } = await params;
if (!hasLocale(lang)) notFound();
return <html lang={lang}>{/* the starter's body, unchanged */}</html>;
}
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.
- 3d ago First seen · 241 lines · 165 tokens per session scan A e8b162c743cb
i18n-seo is a skill published in the GitHub repository textura-agency/next16-claude-starter (137 stars, last pushed 3d ago), licensed Unlicense. It adds 165 tokens to every session and 3,369 once invoked, about $0.0007 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-10-15.
Other skills, from other repositories
chinese-documentation
A Chinese technical-documentation style guide covering spacing, punctuation, numbers, terminology, and links when Chinese and English appear together.
azure-ai-translation-text-py
Azure AI Text Translation SDK for real-time text translation, transliteration, language detection, and dictionary lookup. Use for translating text content in applications. Triggers: "text translation", "translator", "translate text", "transliterate", "TextTranslationClient".
harden
Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready. Use when the user asks to harden, make production-ready, handle edge cases, add error states, or fix overflow and i18n issues.
seedance-vocab-ja
This skill should be used when the user asks for Japanese Seedance 2.0 prompt wording, Japanese cinematic vocabulary, or translation of camera, lighting, action, VFX, audio, and production terms into Japanese.
asc-subscription-localization
Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work.
update-readme
Updates README.md and README.zh-CN.md to reflect the project's current state. Use this skill whenever the user asks to "update the README", "sync the docs", "update documentation", "reflect latest changes in README", or wants both the English and Chinese READMEs to match the current project.