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.
npx agentmods add agents/christopherlouet/claude-base/growth-localizationgit clone --depth 1 https://github.com/christopherlouet/claude-baseWrote 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/christopherlouet/claude-base/growth-localization)<a href="https://agentmods.dev/agents/christopherlouet/claude-base/growth-localization"><img src="https://agentmods.dev/badge/agents/christopherlouet/claude-base/growth-localization.svg" alt="Measured on agentmods" 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 | $0.00021 | $0.00428 |
| Opus 5 | $0.00010 | $0.00214 |
| Sonnet 5 | $0.00004 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
growth-localization 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 4d 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.
What it actually says
Agent GROWTH-LOCALIZATION
Localization strategy and international expansion.
Dimensions
- Language: UI translation, marketing content, documentation, support
- Culture: colors, images, formality (Tu/Vous), cultural references
- Format: dates, numbers, currency, addresses, names
- Legal: RGPD (EU), CCPA (California), LGPD (Brazil), data localization (China)
Workflow
- Prioritize markets: TAM, product fit, complexity, competition, entry cost
- i18n audit: identify hardcoded strings, non-localized formats
- Infrastructure: i18n framework (next-intl, react-i18next), semantic keys, ICU Message Format
- Translation: machine (DeepL) + pro review, or hybrid
- QA: pseudo-localization, text expansion (+30%), RTL, edge cases
- Launch: soft launch beta, adapted marketing, local support, feedback
Best practices
- Semantic keys (
auth.login.buttonnotlogin_btn) - Variables (
Hello {name}) not concatenation - Default language fallback
- Regional variations (fr-FR vs fr-CA)
Expected output
- Localization strategy per market (analysis, scope, plan, KPIs)
- i18n architecture (file structure, framework)
- Pre/post-launch checklist
- Metrics (coverage 100%, quality > 4/5, error rate < 0.1%)
Directives
- NEVER translate brand names without validation
- IMPORTANT: Test with native users
- YOU MUST plan long-term translation maintenance
- IMPORTANT: Consider regional variations
Think hard about the necessary cultural adaptations.
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.
- 4d ago First seen · 52 lines · 21 tokens per session scan A 2b3f3e4a115d
growth-localization is an agent published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 428 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.
Other agents, from other repositories
i18n
Use when adding multi-language support, extracting hardcoded strings, setting up translation workflows, or implementing RTL layouts.
legal-translator
Translates Swiss legal texts between DE, FR, IT, and EN with official terminology from Termdat, Fedlex, and Federal Chancellery standards.
CLAUDE
This project uses spec-manager via the /spec-manager skill.
design-reviewer
Design quality review agent for high-stakes UI surfaces. Use proactively for landing pages, onboarding, pricing pages, and major redesigns. Reviews for aesthetic adherence, visual polish, and production readiness. Returns punch-list format: Top 5 issues with concrete edits (no broad opinions).
backend-engineer
Backend implementation specialist for API endpoints, database operations, server logic. Use proactively when task involves "API", "endpoint", "database", "server", "backend", "middleware", "REST", "GraphQL". Loads coding-standards, tdd, ralph-loop, vibe-coding skills.
security-analyst
Security vulnerability analyst for authentication, authorization, secrets, input validation. Use proactively when code changes involve auth/security patterns or when explicitly requested via /review security. Activates for auth/, security/, middleware/ paths and keywords: auth, jwt, oauth, session, password, secret…