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/hitosea/happy-nextWrote 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/agents/hitosea/happy-next/i18n-translator)<a href="https://agentmods.dev/agents/hitosea/happy-next/i18n-translator"><img src="https://agentmods.dev/badge/agents/hitosea/happy-next/i18n-translator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<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="Reviewed on agentmods" width="80" 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.01448 |
| Opus 5.5 | $0.00000 | $0.00579 |
| Sonnet 5.5 | $0.00000 | $0.00290 |
| Haiku 4.5 | $0.00000 | $0.00145 |
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 2mo 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.
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.
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.
name: i18n-translator description: Use this agent when you need to add new translatable strings to the application or verify existing translations. This includes: adding new UI text that needs to be translated, ensuring translations are consistent across all language files, verifying that translations fit the UI context (headers, buttons, multiline text), and checking that all required languages have the new string. The agent should be called whenever new user-facing text is introduced to the codebase.\n\n\nContext: The user is adding a new feature that requires translatable strings.\nuser: "I need to add a new error message for when the network connection fails during sync"\nassistant: "I'll use the i18n-translator agent to add this error message with appropriate translations for all languages"\n\nSince new user-facing text needs to be added, use the i18n-translator agent to ensure proper translations are added to all language files.\n\n\n\n\nContext: The user is creating a new screen with multiple UI elements.\nuser: "Create a new profile settings screen with a header, description text, and save button"\nassistant: "I've created the screen structure. Now let me use the i18n-translator agent to add all the necessary translations for the UI text"\n\nAfter creating the screen, use the i18n-translator agent to handle all the translatable strings for the new UI elements.\n\n\n\n\nContext: The user notices missing translations.\nuser: "The cancel button on the settings screen shows 'Cancel' in English but is missing in other languages"\nassistant: "I'll use the i18n-translator agent to verify and add the missing translations for the cancel button"\n\nWhen translations are missing or inconsistent, use the i18n-translator agent to fix them across all language files.\n\n tools: Glob, Grep, LS, Read, WebFetch, TodoWrite, WebSearch, BashOutput, KillBash, Edit, MultiEdit, Write, NotebookEdit model: opus color: green
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:
-
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
-
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
-
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
-
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
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.
- 2mo ago First seen · 120 lines · 0 tokens per session scan A e508a6cae3b8
i18n-translator is an agent published in the GitHub repository hitosea/happy-next (63 stars, last pushed 2d ago), 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.
i18n-translator compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| i18n-translatorhitosea/happy-next | Agent | 63 | 2d ago | MIT | A | 0 | Claude Code |
| i18n_specialistjosstei/maestro-orchestrate | Agent | 486 | 4d ago | Apache-2.0 | A | 91 | Claude Code |
| i18n-specialistjosstei/maestro-orchestrate | Agent | 486 | 4d ago | Apache-2.0 | A | 91 | Claude Code |
| translatorhannsxpeter/scriveno | Agent | 12 | 1mo ago | MIT | A | 42 | Claude Code |
| ste-writermryll/skills | Agent | 9 | 21d ago | MIT | A | 87 | Claude Code |
| frontend-engineerfpindej/netrock | Agent | 235 | 4d ago | MIT | A | 39 | Claude Code |
| hlasm-assembler-specialistjosstei/maestro-orchestrate | Agent | 486 | 4d ago | Apache-2.0 | A | 88 | Claude Code |