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.
git clone --depth 1 https://github.com/MN-Lizard-Team/aiyu-multi-agentWrote 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/mn-lizard-team/aiyu-multi-agent/i18n)<a href="https://agentmods.dev/commands/mn-lizard-team/aiyu-multi-agent/i18n"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/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.1 | $0.00000 | $0.00512 |
| Opus 5 | $0.00000 | $0.00256 |
| Sonnet 5 | $0.00000 | $0.00102 |
| Haiku 4.5 | $0.00000 | $0.00051 |
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 7d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/i18n
Internationalization and localization — preparing apps for multiple languages, RTL support, and locale-specific formatting. Used when going global.
⚠️ CURSOR OUTPUT CONTRACT
You MUST start your FIRST response with this exact agent activation line:
🤖 **Active Agent: `i18n-specialist`** | Skills: `clean-code, i18n-localization, frontend-design`
If this line is missing from your response, you are violating the protocol. Add it before any other content.
Required Behavior
- Follow the task steps defined below
- Apply the Socratic Gate: ask clarifying questions if requirements are unclear
- Report completion status at the end
/i18n — Internationalization & Localization
$ARGUMENTS
🤖 Agent Activation
MANDATORY: Before starting any work, announce the active agent to the user.
🤖 **Active Agent: `i18n-specialist`** | Skills: `clean-code, i18n-localization, frontend-design`
Task
Prepare application for multiple languages and regions. Detect hardcoded strings, set up translation infrastructure, and ensure locale-aware formatting.
Steps:
-
Audit Current State
- Detect hardcoded strings
- Check date/number/currency formatting
- Test RTL readiness
-
i18n Architecture
- Set up translation file structure
- Configure i18n library (react-i18next, next-intl, etc.)
- Implement locale detection + fallback chain
-
String Extraction
- Move all text to translation files
- Use ICU MessageFormat for plurals + interpolation
- Add context to keys (not
btn1, useuser.profile.save_button)
-
Layout Adaptation
- RTL support (Arabic, Hebrew)
- Text expansion buffer (German +30%)
- Flexible containers (no fixed-width text)
-
Verification
- Pseudolocalization test (accented chars)
- RTL layout test
- Date/number/currency format test per locale
Usage Examples
/i18n audit hardcoded strings in this project
/i18n set up react-i18next for 5 languages
/i18n add RTL support for Arabic
/i18n configure date and currency formatting
/i18n extract strings from component files
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.
- 7d ago First seen · 82 lines · 0 tokens per session scan A 4e0da6c57882
i18n is a command published in the GitHub repository MN-Lizard-Team/aiyu-multi-agent (7 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 512 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-08-31.
Other commands, from other repositories
dashboard-session-abort-all
Abort multiple running sessions (asks which). Usage /dashboard:session-abort-all.
dashboard-session-rename
Rename a session. Usage /dashboard:session-rename.
dashboard-server-tunnel-status
Tunnel status + public URL. Runs locally, no LLM.
nav-graph
Extract, inspect, and query the app navigation graph — a complete map of all screens and navigators.
rn-feature-dev
Guided feature development for React Native — explore codebase, design architecture, implement, verify live on device, and review quality.
i18n
Set up internationalization architecture. Usage - /mindforge:i18n [app] [--format icu] [--locales en,fr,ja] [--lazy-load].