i18n

i18n is a command for Claude Code, Cursor from MN-Lizard-Team/aiyu-multi-agent. It costs 0 tokens per session (512 once invoked), scanned A, original, Apache-2.0.

A command for preparing an application to support multiple languages and regional settings. Internationalization means building the app for translation, while localization adapts text and formats such as dates, numbers, and currencies.

In plain words
What is it for?
Use it to audit strings, introduce translation support, and review date, number, currency, and right-to-left formatting for a global application.
Why use it?
It helps reveal hardcoded text and formatting that would break when the app is translated or used in another region. It also sets expectations for right-to-left languages and locale-aware display.

Command for Claude CodeCursor

Written for Claude Code and Cursor: $ARGUMENTS substitution, but also installed under .cursor/.

Good fit Use it to audit strings, introduce translation support, and review date, number…

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/mn-lizard-team/aiyu-multi-agent/i18n
Install

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.

Clone the repo
git clone --depth 1 https://github.com/MN-Lizard-Team/aiyu-multi-agent

Made for: Claude Code, Cursor.

Wrote 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.

agentmods badge for i18n

README.md
[![agentmods](https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/i18n.svg)](https://agentmods.dev/commands/mn-lizard-team/aiyu-multi-agent/i18n)
Your own site
<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>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 512 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 7d ago against content hash 4e0da6c57882, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

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.

.cursor/commands/i18n.md · 82 lines

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

  1. Follow the task steps defined below
  2. Apply the Socratic Gate: ask clarifying questions if requirements are unclear
  3. 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:

  1. Audit Current State

    • Detect hardcoded strings
    • Check date/number/currency formatting
    • Test RTL readiness
  2. i18n Architecture

    • Set up translation file structure
    • Configure i18n library (react-i18next, next-intl, etc.)
    • Implement locale detection + fallback chain
  3. String Extraction

    • Move all text to translation files
    • Use ICU MessageFormat for plurals + interpolation
    • Add context to keys (not btn1, use user.profile.save_button)
  4. Layout Adaptation

    • RTL support (Arabic, Hebrew)
    • Text expansion buffer (German +30%)
    • Flexible containers (no fixed-width text)
  5. 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

Read the full file on GitHub · 82 lines

Changes

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.

  1. 7d ago First seen · 82 lines · 0 tokens per session scan A 4e0da6c57882

Subscribe to this mod's changes

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.