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 hamzaPixl/pixl-ai --skill i18n-setupgit clone --depth 1 https://github.com/hamzaPixl/pixl-aiWrote 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/hamzapixl/pixl-ai/i18n-setup)<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/i18n-setup"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/i18n-setup/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/hamzapixl/pixl-ai/i18n-setup"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/i18n-setup.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.00047 | $0.01027 |
| Opus 5.5 | $0.00019 | $0.00411 |
| Sonnet 5.5 | $0.00009 | $0.00205 |
| Haiku 4.5 | $0.00005 | $0.00103 |
Grade A, and why
i18n-setup 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 1mo 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup
Read config.json in this skill directory (if it exists):
locales— target locale list; default ["en", "fr", "nl"]default_locale— fallback locale; default "en"library— i18n library preference; default "next-intl"
If the argument provides locales (e.g. /i18n-setup en,fr,de), override the config defaults.
If neither argument nor config provides locales, use AskUserQuestion:
"Which locales should this project support? (comma-separated BCP-47 codes, e.g. en,fr,nl)"
Overview
Adds internationalization (i18n) to a Next.js application supporting EN/FR/NL. Covers infrastructure setup, translation extraction, component integration, and optional CMS/MDX content migration.
Required References
Before starting, read references/frontend/i18n-conventions.md for locale file structure, key naming, and pluralization patterns.
Step 1: Discovery
- Analyze existing Next.js configuration (App Router vs Pages Router)
- Identify all user-facing strings in the codebase
- Check for existing i18n setup or library
- Determine content sources (hardcoded, CMS, MDX)
- Count translatable strings for scope estimation
Step 2: Infrastructure
- Install and configure i18n library (next-intl or similar)
- Set up locale routing (
/en/...,/fr/...,/nl/...) - Create translation file structure (
messages/en.json,messages/fr.json,messages/nl.json) - Add locale detection and switching
- Configure middleware for locale routing
Step 3: Translation Extraction (Parallel — 3 Agents)
Spawn 3 Explore agents to scan the codebase in parallel:
- Extract all hardcoded strings from components
- Generate translation keys following a consistent naming convention
- Create initial translation files with English as source
Step 4: Translation Quality Pass
After generating English source strings, translate to each target locale with these mandatory rules:
French (fr)
- All diacritics are required — never omit accents: é è ê ë à â ç ù û ô î ï œ æ
- Common mistakes to avoid:
- "évenement" → événement, "parametre" → paramètre, "creer" → créer
- "deja" → déjà, "a" (preposition) vs à, "ou" (or) vs où (where)
- Past participles: "termine" → terminé, "supprime" → supprimé
- Sentence structure: French uses spaces before
:,!,?,;(thin non-breaking space\u202Fpreferred) - Use « guillemets » for quotes, not "English quotes"
What ships with it
1 file 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.
- 1mo ago First seen · 103 lines · 47 tokens per session scan A 8601937d4dca
i18n-setup is a skill published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 6mo ago), licensed MIT. It adds 47 tokens to every session and 1,027 once invoked, about $0.0002 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
intl-expansion
International market expansion strategy. Market selection, entry modes, localization, regulatory compliance, and go-to-market by region. Use when expanding to new countries, evaluating international markets, planning localization, or building regional teams.
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.
edit-site
Plans, coordinates and customizes PAC CLI-downloaded Standard or Enhanced data model non-SPA Power Pages sites created from Microsoft templates or manually in Design Studio. Use for requests involving pages, localized content, navigation, assets, snippets, site markers, Liquid/web templates, page layouts, or styling.…
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.