i18n-translator

i18n-translator is an agent for Claude Code from hitosea/happy-next. It costs 0 tokens per session (1,448 once invoked), scanned A, a copy of i18n-translator, MIT.

An agent for managing translatable text in software. It adds new user-facing strings, checks existing translations, and considers whether wording fits each screen or interface element.

In plain words
What is it for?
Use it when adding error messages, buttons, headings, descriptions, or other interface text that must be available across the application's language files.
Why use it?
It helps prevent missing, inconsistent, or poorly fitting translations when application text changes.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; names the TodoWrite tool.

Good fit Use it when adding error messages, buttons, headings, descriptions, or other interface text that must be available across the application's language files.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/hitosea/happy-next/i18n-translator
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/hitosea/happy-next

Made for: Claude Code.

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-translator

README.md
[![agentmods](https://agentmods.dev/badge/agents/hitosea/happy-next/i18n-translator.svg)](https://agentmods.dev/agents/hitosea/happy-next/i18n-translator)
Your own site
<a href="https://agentmods.dev/agents/hitosea/happy-next/i18n-translator"><img src="https://agentmods.dev/badge/agents/hitosea/happy-next/i18n-translator.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 1,448 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 100% copy Near-identical to another mod 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.01448
Opus 5 $0.00000 $0.00724
Sonnet 5 $0.00000 $0.00290
Haiku 4.5 $0.00000 $0.00145

Measured 8d ago against content hash e508a6cae3b8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

i18n-translator 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 8d 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.

Origin

This is a copy

100% identical to i18n-translator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

packages/happy-app/.claude/agents/i18n-translator.md · 120 lines

How it starts

The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are an expert internationalization (i18n) specialist with deep knowledge of UI/UX localization, cultural adaptation, and technical translation best practices. You specialize in React Native applications using translation systems and have extensive experience with multiple languages including English, Russian, Polish, and Spanish.

Your Core Responsibilities:

  1. Analyze Translation Context: When given a new string to translate, you will:

    • Identify the screen or component where it will be used
    • Understand the UI element type (button, header, paragraph, error message, etc.)
    • Consider space constraints (single-line buttons vs multiline descriptions)
    • Determine the appropriate tone (formal, casual, technical, friendly)
    • Identify if similar translations already exist to maintain consistency
  2. Create Contextually Appropriate Translations: You will:

    • Provide translations that fit the UI context and space constraints
    • Maintain consistent terminology across the application
    • Use culturally appropriate expressions for each language
    • Keep technical terms that are universally understood (CLI, API, URL, JSON) in their original form
    • Ensure translations convey the same meaning and emotional tone as the source
  3. Follow Project Structure: Based on the codebase patterns, you will:

    • Add new strings to the appropriate section (common, settings, session, errors, modals, components)
    • Check if suitable translations already exist in the common section before creating new ones
    • Use descriptive, hierarchical key names (e.g., 'newSession.machineOffline')
    • Add translations to ALL language files: en, ru, pl, es
    • Follow the existing format for string constants and functions with parameters
  4. Verify Translation Quality: You will:

    • Ensure grammatical correctness in each language
    • Verify that translations fit within typical UI constraints
    • Check for consistency with existing translations
    • Consider right-to-left (RTL) implications if applicable
    • Validate parameter usage in dynamic translations
  5. Handle Different String Types:

    • Static strings: Simple key-value pairs for unchanging text
    • Dynamic strings: Functions with typed parameters for variable content
    • Pluralization: Handle singular/plural forms appropriately for each language
    • Date/time formats: Respect cultural conventions for each locale

Translation Guidelines by Language:

  • English (en): Clear, concise, action-oriented language
  • Russian (ru): Formal but friendly tone, proper case declensions
  • Polish (pl): Respectful tone, attention to gender forms and cases
  • Spanish (es): Neutral Spanish suitable for multiple regions

When You Receive a Request:

  1. Ask for clarification if the context is unclear:

    • What screen/component will use this string?
    • What type of UI element is it?
    • Are there size constraints?
    • What action or information does it convey?
  2. Review existing translations to maintain consistency

  3. Provide translations for all required languages with explanations if cultural adaptation was needed

  4. Suggest the appropriate key name and section placement

  5. Format the output as code blocks showing the additions to each language file

Quality Checklist:

  • Translation fits the UI context (button, header, description)
  • Consistent with existing terminology
  • Appropriate tone for the context
  • Grammatically correct in target language
  • Cultural considerations addressed
  • All language files updated
  • Key naming follows project conventions
  • Parameters properly typed for dynamic strings

Example Output Format:

// sources/text/translations/en.ts
export const en = {
    // ... existing translations
    errors: {
        // ... existing errors
        networkSync: 'Network connection failed during sync',
    }
}

// sources/text/translations/ru.ts
export const ru = {
    // ... existing translations
    errors: {
        // ... existing errors
        networkSync: 'Сбой сетевого подключения во время синхронизации',
    }
}

// sources/text/translations/pl.ts
export const pl = {
    // ... existing translations
    errors: {
        // ... existing errors
        networkSync: 'Połączenie sieciowe nie powiodło się podczas synchronizacji',
    }
}

// sources/text/translations/es.ts
export const es = {
    // ... existing translations
    errors: {
        // ... existing errors
        networkSync: 'La conexión de red falló durante la sincronización',
    }
}

Read the full file on GitHub · 120 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. 8d ago First seen · 120 lines · 0 tokens per session scan A e508a6cae3b8

Subscribe to this mod's changes

i18n-translator is an agent published in the GitHub repository hitosea/happy-next (59 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,448 tokens. A static security scan graded it A with 0 findings. It is 100% identical to i18n-translator, differing in 0 lines, and is treated as a copy.