agentmods.dev

i18n-specialist

i18n-specialist is an agent for Claude Code from atretyak1985/swarmery. It costs 23 tokens per session (1,787 once invoked), scanned A, original, Apache-2.0.

An agent for managing translations in a web application. It checks that supported languages, such as English and Ukrainian, have matching text and that visible messages use translation files.

In plain words
What is it for?
Use it to audit translation coverage, add translated strings, find hardcoded interface text, and reorganize translation keys.
Why use it?
It helps prevent missing translations, inconsistent wording, and user-facing text that is accidentally fixed to one language.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; mentions CLAUDE.md.

Part of the web-pack plugin — 1 command, 3 agents shipped together

not rated 5repo +1 yesterday A scan 23 tokens original Apache-2.0

Good fit Use it to audit translation coverage, add translated strings, find hardcoded interface text, and reorganize translation keys.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/atretyak1985/swarmery/i18n-specialist
View source ↗ atretyak1985/swarmery atretyak1985.github.io
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/atretyak1985/swarmery

Made for: Claude Code.

Or install web-pack, the plugin that ships this one along with the rest of its 1 command, 3 agents.

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/atretyak1985/swarmery/i18n-specialist/github.svg)](https://agentmods.dev/agents/atretyak1985/swarmery/i18n-specialist)
Your own site
<a href="https://agentmods.dev/agents/atretyak1985/swarmery/i18n-specialist"><img src="https://agentmods.dev/badge/agents/atretyak1985/swarmery/i18n-specialist/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.

agentmods 80×15 button for i18n-specialist

Your own site · 80×15
<a href="https://agentmods.dev/agents/atretyak1985/swarmery/i18n-specialist"><img src="https://agentmods.dev/badge/agents/atretyak1985/swarmery/i18n-specialist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 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,787 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.00023 $0.01787
Opus 5 $0.00012 $0.00894
Sonnet 5 $0.00005 $0.00357
Haiku 4.5 $0.00002 $0.00179

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

Security

Grade A, and why

i18n-specialist 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.

plugins/web-pack/agents/i18n-specialist.md · 207 lines

How it starts

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

When to Use

  • Adding new user-facing strings to components
  • Auditing translation coverage (en vs uk)
  • Fixing missing or inconsistent translation keys
  • Restructuring translation files for better maintainability
  • Reviewing components for hardcoded strings
  • After any UI change that introduces new text

How to Invoke

@i18n-specialist audit translation coverage
@i18n-specialist add translations for the new pricing section
@i18n-specialist find hardcoded strings in components
@i18n-specialist restructure translation keys for features section

Agent Context

You are an i18n Specialist for the project's web apps, ensuring complete and consistent internationalization across the supported languages (e.g. English en and Ukrainian uk — see the project's CLAUDE.md).

Technology Stack

  • Library: react-i18next with i18next
  • Translation files: src/i18n/en.ts and src/i18n/uk.ts
  • Language detection: querystring (?lng=), localStorage (project-prefixed key, e.g. <project>_lang), browser navigator
  • HTML sync: <html lang> attribute updates on language change

Key Principles

  • Never hardcode user-facing strings — always use t() from useTranslation()
  • Keys must exist in both languages — en and uk must have identical key structures
  • Nested keys for organization — group by feature/section (e.g., hero.title, pricing.plan1.name)
  • Interpolation for dynamic values — use {{variable}} syntax, not string concatenation
  • Pluralization support — use i18next plural rules where needed
  • Keep translations human-readable — avoid overly technical keys

Workflow

Step 1: Audit Current State

  1. Read src/i18n/en.ts and src/i18n/uk.ts
  2. Compare key structures — find missing keys in either language
  3. Grep components for useTranslation usage
  4. Grep for hardcoded strings (text outside t() calls)

Step 2: Identify Gaps

  • Missing keys in uk that exist in en (or vice versa)
  • Hardcoded strings in JSX that should use t()
  • Inconsistent key naming patterns
  • Unused translation keys (keys not referenced in any component)

Read the full file on GitHub · 207 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 · 207 lines · 23 tokens per session scan A 48fabaa6138b

Subscribe to this mod's changes

i18n-specialist is an agent published in the GitHub repository atretyak1985/swarmery (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 23 tokens to every session and 1,787 once invoked, about $0.0001 per session on Opus 5. 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.

Claude CodeLocalizationagentsai-agentsclaude-code-pluginsplugin-marketplace
Related

Other agents, from other repositories

i18n-specialist

Expert internationalization specialist for multi-language support and localization.

travisjneuman/.claude · 16 tokens

docs-scribe

Use this agent to maintain the inward-facing documentation that lives inside fakoli-state: the docs/ folder (specs, runbooks, design notes, plan archives), the plugin's CHANGELOG.md, and the description field of .claude-plugin/plugin.json. Audits cross-references between docs — broken [[wikilinks]], mismatched section…

fakoli/fakoli-plugins · 723 tokens

marketplace-scribe

Use this agent to maintain the marketplace-level artifacts that surface fakoli-state to first-time visitors: .claude-plugin/marketplace.json, the root README.md plugins table, and the registry/.json index files. Fires after any version bump, agent add/remove, or skill add/remove inside fakoli-state — these are the…

fakoli/fakoli-plugins · 657 tokens

warden

Use this agent when you need a security review — injection surfaces, secret and credential leakage, dependency and supply-chain risk, and plugin permission surfaces (hooks, tool allowlists, MCP configs). Wardens report; they don't fix. Context: A new feature added an endpoint that shells out based on user input. user…

fakoli/fakoli-plugins · 389 tokens

planner

Use this agent when you need to turn a parsed fakoli-state PRD into a coherent task graph — propose Features that group related Requirements, draft Tasks with acceptance criteria and verification commands, and surface high-complexity tasks that should be expanded. Specializes in the PRD-to-tasks transformation; defers…

fakoli/fakoli-plugins · 396 tokens

audit-global

Audits global Claude Code configuration (/.claude/) against expert knowledge. Dispatched by /claudit during Phase 2.

acostanzo/quickstop · 29 tokens