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 int2t05/engineering-skills --skill i18ngit clone --depth 1 https://github.com/int2t05/engineering-skillsWrote 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/int2t05/engineering-skills/i18n)<a href="https://agentmods.dev/skills/int2t05/engineering-skills/i18n"><img src="https://agentmods.dev/badge/skills/int2t05/engineering-skills/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/int2t05/engineering-skills/i18n"><img src="https://agentmods.dev/badge/skills/int2t05/engineering-skills/i18n.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.00025 | $0.00273 |
| Opus 5.5 | $0.00010 | $0.00109 |
| Sonnet 5.5 | $0.00005 | $0.00055 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
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 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.
What it actually says
Internationalization (i18n)
When to use
- Implement or audit localization for supported product locales.
Not for: frontend-design for general layout.
Steps
-
Identify actual locales, tooling, translation ownership and affected surfaces.
-
Extract messages and use locale-aware pluralization, dates, numbers and routing in the actual rendering model.
-
Handle expansion, fonts, accessibility and fallbacks; add or test RTL only when relevant to supported locales.
-
Exercise translations, missing messages, locale persistence and relevant server/client boundaries.
Verify
- Supported messages and formatting are correct; routing and layout evidence covers actual locale requirements.
References
- engineering-principles.md — shared decision boundaries, scope and verification.
- references/i18n-checklist.md — locale-surface audit template, ICU syntax reference, RTL conversion checklist, locale-detection patterns, test-locale matrix
- references/server-i18n.md — RSC / App Router message loading, per-locale bundle splitting, request-scoped locale, hydration alignment
What ships with it
3 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 Changed · -107 lines · -43 tokens per session 499538990794
- 2mo ago First seen · 140 lines · 68 tokens per session scan A d97c26f8d853
i18n is a skill published in the GitHub repository int2t05/engineering-skills (3 stars, last pushed 17d ago), licensed MIT. It adds 25 tokens to every session and 273 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-08-31.
Other skills, from other repositories
review-all
Multi-agent code review for diffs (project-agnostic). Covers standards, bugs, security, DRY, smells, perf, tests, API contracts, a11y/i18n. Verifies each finding to eliminate false positives. Use for /review-all, pre-PR/pre-commit review, or auditing uncommitted/staged changes.
design-reviewer
Use after AC and before RED for any wave that ships UI or changes existing behaviour. Audits component APIs against installed dist files, writes a per-route mockup and visual ACs to .wave/dr.md.
test-audit
Audit test suites for T1-T4 violations using AST analysis, mock detection, and multi-stage synthesis. Invoke when user asks to audit tests, check test quality, find mock violations, review test effectiveness, or inspect test suites for over-mocking. Triggers automatic rewrites when quality gates fail.
plan
Analyzes architecture, selects patterns, assesses testability, then decomposes work into ordered TDD tasks with exact verification commands and explicit acceptance mapping. Works from an approved spec (zuvo:brainstorm output) or directly from a user-provided description.
Eval-Driven Skill Design
A review guide for new coding-agent skills that checks whether each skill has both examples it should catch and examples it should ignore, plus evaluation setup.
validate-plan
Validate implementation plans against DRY, YAGNI, TDD principles and best practices. Use when reviewing plans from pocket-planning or another planning workflow to identify gaps, anti-patterns, and improvement opportunities before execution.