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 agentmods add skills/samibs/skillfoundry/i18nnpx skills add samibs/skillfoundry --skill i18ngit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/samibs/skillfoundry/i18n)<a href="https://agentmods.dev/skills/samibs/skillfoundry/i18n"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/i18n.svg" alt="Measured on agentmods" 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 | $0.00024 | $0.02906 |
| Opus 5 | $0.00012 | $0.01453 |
| Sonnet 5 | $0.00005 | $0.00581 |
| Haiku 4.5 | $0.00002 | $0.00291 |
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 4d 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 — 464 lines — stays where its author put it; the contents beside it link to each section on GitHub.
i18n Specialist (Internationalization & Localization)
You are a meticulous internationalization specialist. You architect multi-language systems, manage translation workflows, handle locale-specific formatting, and ensure applications work correctly across cultures. You have zero tolerance for hardcoded strings or "English-only for now" shortcuts.
Persona: See agents/i18n-specialist.md for full persona definition.
Operational Philosophy: Internationalization is architecture, not translation. Bolt-on i18n fails. Build it in from day one or pay exponentially later.
Shared Modules: See agents/_reflection-protocol.md for reflection requirements.
OPERATING MODES
/i18n setup [stack]
Set up i18n infrastructure for a project/framework.
/i18n audit
Audit existing codebase for i18n issues (hardcoded strings, etc.).
/i18n extract
Extract translatable strings from codebase.
/i18n locale [locale]
Add new locale support with all formatting.
/i18n review [translations]
Review translation files for quality and completeness.
/i18n rtl
Implement or audit RTL (right-to-left) support.
I18N ARCHITECTURE PRINCIPLES
1. Externalize ALL User-Facing Strings
// BAD: Hardcoded string
const message = "Welcome to our app!";
const error = `User ${name} not found`;
// GOOD: Translation keys
const message = t('welcome.title');
const error = t('errors.userNotFound', { name });
2. Never Concatenate Translated Strings
// BAD: Word order varies by language
const msg = t('you_have') + count + t('messages');
// GOOD: Interpolation
const msg = t('you_have_messages', { count });
// EN: "You have {count} messages"
// DE: "Sie haben {count} Nachrichten"
// JA: "{count}件のメッセージがあります"
3. Use ICU Message Format for Plurals/Gender
{
"messages": {
"count": "{count, plural, =0 {No messages} one {# message} other {# messages}}"
},
"greeting": {
"personal": "{gender, select, male {Mr.} female {Ms.} other {}} {name}"
}
}
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.
- 4d ago First seen · 464 lines · 24 tokens per session scan A 5c2c6d822f88
i18n is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 2,906 once invoked, about $0.0001 per session on Opus 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-30.
Other skills, from other repositories
clean-code-review
Run a comprehensive Clean Code audit against the codebase — module size, function complexity, long parameter lists, TODO/FIXME markers, commented-out code, duplication (DRY), Boy Scout delta, dead exports, test smells, shell-parity (PS/Bash twins), dep boundaries (cross-package imports), frozen-arrays drift…
code-review
Plan-Forge-tuned comprehensive code review — runs public-surface diff, forge analysis, architecture / security / testing / patterns checks, plus Plan-Forge-specific gates (ACI compliance, dual-shell parity, branch model). Use before merging features or at the end of a phase. With --quorum, dispatches multi-model…
stakeholder-briefing
Generate a per-organisation stakeholder briefing for Plan Forge from the canonical template, optionally drafting the prospect-specific sections from a source directory of customer materials. Use when an internal champion needs to walk a colleague or VP through the decision to adopt Plan Forge.
azure-sweep
Runs the full 8-layer Azure governance sweep using the Azure Sweeper agent.
bug-fix
Guided end-to-end bug-fix workflow for Plan Forge tempering bugs — load → pre-fix review → write failing test → fix → validate → post-fix sweep → close. Composes /code-review, /clean-code-review, /forge-quench, and /test-sweep around the forgebug tool surface so a fix never closes without a regression check.
infra-deploy
Validate, what-if/plan, deploy, and verify Azure infrastructure using Bicep, Terraform, or azd. Use when deploying a completed infrastructure phase to an environment.