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 fusengine/agents --skill nextjs-i18ngit clone --depth 1 https://github.com/fusengine/agentsWrote 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/fusengine/agents/nextjs-i18n)<a href="https://agentmods.dev/skills/fusengine/agents/nextjs-i18n"><img src="https://agentmods.dev/badge/skills/fusengine/agents/nextjs-i18n/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/fusengine/agents/nextjs-i18n"><img src="https://agentmods.dev/badge/skills/fusengine/agents/nextjs-i18n.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00035 | $0.01537 |
| Opus 5.5 | $0.00014 | $0.00615 |
| Sonnet 5.5 | $0.00007 | $0.00307 |
| Haiku 4.5 | $0.00003 | $0.00154 |
Grade A, and why
nextjs-i18n 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 29d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Covers [locale]-prefixed routing, localized navigation components (Link, redirect, usePathname, useRouter), date/number/currency/relative-time formatting, RTL language support, SEO hreflang tags, and localized special files ([locale]/error.tsx, [locale]/not-found.tsx, global-error.tsx). This is the Next.js-specific i18n skill (App Router routing, proxy.ts integration) — for plain React apps without Next.js see react-i18n, and for Astro see astro-i18n.
Next.js 16 Internationalization
Complete i18n solution with next-intl or DIY dictionary approach.
Agent Workflow (MANDATORY)
Before ANY implementation, spawn 3 agents in parallel, one Agent call each with a name:
- fuse-ai-pilot:explore-codebase - Analyze existing i18n setup and message files
- fuse-ai-pilot:research-expert - Verify latest next-intl docs via Context7/Exa
- mcp__context7__query-docs - Check locale config and patterns
After implementation, run fuse-ai-pilot:sniper for validation.
Overview
When to Use
- Building multilingual Next.js 16 applications
- Need locale-based routing with
[locale]dynamic segment - Implementing language switcher and URL localization
- Formatting dates, numbers, currencies, and relative times per locale
- SEO optimization with hreflang tags and localized metadata
- Supporting right-to-left (RTL) languages
Why next-intl
| Feature | Benefit |
|---|---|
| App Router native | Full Server Components support |
| Type-safe messages | TypeScript autocompletion for keys |
| ICU MessageFormat | Pluralization, gender, select expressions |
| Async message loading | Load translations on-demand per locale |
| proxy.ts compatible | Works with Next.js 16 proxy pattern |
| Rich formatting | Dates, numbers, lists, relative time |
What ships with it
23 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/client-components.md 2.7 KB
- references/configuration.md 3.0 KB
- references/core-library.md 2.0 KB
- references/diy-dictionaries.md 2.5 KB
- references/diy-locale-detection.md 2.9 KB
- references/error-files.md 2.1 KB
- references/extraction.md 2.6 KB
- references/formatting.md 2.3 KB
- references/installation.md 2.3 KB
- references/integrations.md 2.0 KB
- references/messages-validation.md 2.4 KB
- references/middleware-proxy.md 2.5 KB
- references/navigation.md 2.6 KB
- references/pages-router.md 2.4 KB
- references/plugin.md 1.8 KB
- references/routing-config.md 2.5 KB
- references/routing-setup.md 2.6 KB
- references/runtime-requirements.md 2.0 KB
- references/seo.md 2.5 KB
- references/server-components.md 2.8 KB
- references/testing.md 2.6 KB
- references/translations.md 2.2 KB
- references/typescript.md 2.4 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.
- 29d ago Changed 471ea8165b6d
- 1mo ago Changed f4ae899dd197
- 1mo ago First seen · 167 lines · 35 tokens per session scan A eee5eafd4568
nextjs-i18n is a skill published in the GitHub repository fusengine/agents (34 stars, last pushed 14d ago), licensed MIT. It adds 35 tokens to every session and 1,537 once invoked, about $0.0001 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-03.
Other skills, from other repositories
improve-search-visibility-entity-footprint
Step of the improve-search-visibility playbook: checks the profiles answer engines read, plus local listings and reviews, against the brand's facts and writes corrections. Run improve-search-visibility instead; not for direct use.
radin-stats
Use for /radin-stats. Shows the stats or gain output of every companion tool that ships one, side by side.
ccpa-compliance
Analyze CCPA/CPRA obligations legally — applicability thresholds, consumer-rights procedures, notice at collection, the Do Not Sell or Share link, and service-provider contract terms. Use when the user needs to know whether CCPA applies and what their notices, request procedures and vendor contracts must say. Not for…
data-processing-agreement
Draft a GDPR Article 28 Data Processing Agreement — controller and processor roles, processing details, processor obligations, sub-processors, breach notice, audit rights, deletion and international transfers. Use when a customer asks the user to sign a DPA, or the user needs one for a vendor that handles their…
gdpr-compliance
Analyze GDPR obligations legally — data mapping, lawful basis, DPIA and DPO needs, data subject rights procedures, breach notification, transfer mechanisms and Article 30 records. Use when the user asks how to legitimize EU data transfers, whether they need a DPIA or DPO, or what GDPR legally requires of them. Not for…
compliance-monitor
Design a legal team's ongoing compliance oversight — monitoring scope per regulation, owners, escalation levels, board reporting and a compliance calendar. Use when the user needs to decide who owns each regulation, how non-compliance escalates and which legal deadlines to calendar. Not for automated control checks…