translate

A workflow for finding hardcoded text in an app and preparing it for translation with i18next-cli, a command-line tool for managing i18next translations.

In plain words
What is it for?
Use it to scan a monolithic app or monorepo, locate translation configuration, and fix strings that are not yet wired into the translation system.
Why use it?
It detects the right app directory and package manager, then establishes a baseline so translation changes can be checked.

Command

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.

agentmods
npx agentmods add commands/basaltbytes/agentic-tools/translate
Clone the repo
git clone --depth 1 https://github.com/basaltbytes/agentic-tools
Per session 17 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,027 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00017 $0.01027
Opus 5 $0.00009 $0.00513
Sonnet 5 $0.00003 $0.00205
Haiku 4.5 $0.00002 $0.00103

Measured yesterday against content hash d72a1a2aecba, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

translate 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 yesterday.

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.

i18next-translate-plugin/commands/translate.md · 174 lines

How it starts

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

Translation Workflow for i18next

You are running a translation workflow to find and fix hardcoded strings using i18next-cli.

Arguments

  • $ARGUMENTS - Optional path to app directory (for monorepos), e.g., apps/mobile

Step 1: Detect Project Structure

First, determine where to run commands:

# If path provided, cd into it
# Otherwise, check current directory for config
find . -maxdepth 3 -name "i18next.config.ts" -o -name "i18next.config.js" -o -name "i18next.config.mjs" 2>/dev/null | head -10

Determine project type:

  • Monolith: Config at project root → work from root
  • Monorepo: Config in apps/* or packages/* → cd into that directory

If no config found, ask user if they want to create one with npx i18next-cli init.

Step 2: Detect Package Manager

# Check lockfiles to determine package manager
if [ -f "pnpm-lock.yaml" ]; then
  echo "pnpm"
elif [ -f "yarn.lock" ]; then
  echo "yarn"
else
  echo "npm"
fi

Use the appropriate runner:

  • pnpm → pnpm dlx i18next-cli or pnpm i18next-cli if installed
  • yarn → yarn dlx i18next-cli
  • npm → npx i18next-cli

Step 3: Check Initial Status

Get baseline translation status:

<package-runner> i18next-cli status

Report to user:

  • Overall progress per locale (%)
  • Number of missing keys
  • Which namespaces need attention

Step 4: Self-Verification Loop

Enter the fix-and-verify loop:

4a. LINT - Find Hardcoded Strings

<package-runner> i18next-cli lint

Parse the output to identify:

  • File paths with issues
  • Line numbers
  • The hardcoded text

4b. FIX - Apply Translations

For each hardcoded string found, apply the appropriate fix:

Plain text in JSX:

// ❌ Before
<Text>Welcome back!</Text>

// ✅ After  
<Text>{t('welcome_back')}</Text>

Text with interpolation:

// ❌ Before
<Text>Hello {userName}!</Text>

// ✅ After
<Text>{t('hello_user', { name: userName })}</Text>

Rich text with nested elements (use Trans component):

// ❌ Before
<Text>Read our <Link>terms</Link></Text>

// ✅ After
import { Trans } from 'react-i18next';
<Trans i18nKey="read_terms">
  Read our <Link>terms</Link>
</Trans>

Read the full file on GitHub · 174 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. yesterday First seen · 174 lines · 17 tokens per session scan A d72a1a2aecba

Subscribe to this mod's changes

translate is a command published in the GitHub repository basaltbytes/agentic-tools (2 stars, last pushed 7mo ago), licensed MIT. It adds 17 tokens to every session and 1,027 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-08-31.