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 commands/samibs/skillfoundry/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/commands/samibs/skillfoundry/i18n)<a href="https://agentmods.dev/commands/samibs/skillfoundry/i18n"><img src="https://agentmods.dev/badge/commands/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.00000 | $0.02873 |
| Opus 5 | $0.00000 | $0.01437 |
| Sonnet 5 | $0.00000 | $0.00575 |
| Haiku 4.5 | $0.00000 | $0.00287 |
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 yesterday.
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 — 458 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.
- yesterday First seen · 458 lines · 0 tokens per session scan A a6b49e21f2c4
i18n is a command published in the GitHub repository samibs/skillfoundry (12 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,873 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.