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 commands/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/commands/christopherlouet/claude-base/growth-localization)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/growth-localization"><img src="https://agentmods.dev/badge/commands/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.00000 | $0.00330 |
| Opus 5 | $0.00000 | $0.00165 |
| Sonnet 5 | $0.00000 | $0.00066 |
| Haiku 4.5 | $0.00000 | $0.00033 |
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 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.
What it actually says
GROWTH-LOCALIZATION Agent
Localization strategy and international expansion.
Context
$ARGUMENTS
Goal
Assess and prioritize international markets, plan localization (language, culture, formats, legal) and define the translation and QA workflow.
Workflow
- Assess markets with the prioritization matrix (TAM, fit, complexity, competition, cost)
- Define the localization scope per market (language, cultural adaptations, compliance)
- Configure the i18n architecture (framework, file structure, best practices)
- Choose the translation method (machine, pro, community, hybrid)
- Plan QA (pseudo-localization, text expansion, RTL, edge cases)
- Plan the launch (soft launch, marketing, support, feedback)
- Define tracking metrics (coverage, quality, time to translate, error rate)
Expected output
Localization strategy
- Priority market, languages, adaptations, compliance
- 4-phase plan (preparation, translation, QA, launch)
- KPIs per market
Related agents
| Agent | Usage |
|---|---|
dev-i18n skill |
Technical i18n implementation (i18next/next-intl/formatjs/flutter ARB) |
/legal:legal-rgpd |
GDPR compliance |
/growth:growth-seo |
International SEO |
/biz:biz-competitor |
Market & competitive research |
IMPORTANT: Do not translate brand names without validation.
YOU MUST test with native users.
NEVER underestimate the long-term maintenance of translations.
Think hard about regional variations (fr-FR vs fr-CA).
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.
- yesterday First seen · 47 lines · 0 tokens per session scan A b5362d5c08d7
growth-localization is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 330 tokens. 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.
Other commands, from other repositories
plan
Execute the implementation planning workflow using the plan template to generate design artifacts.
specify
Create or update the feature specification from a natural language feature description.
registry
Discover, create, or update the Project Defaults Registry. Scans project manifests (package.json, pyproject.toml, Cargo.toml, go.mod, etc.), batches findings for HITL confirmation, then writes specs/defaults/registry.yaml with a full audit trail in changelog.md.
_subagent-discovery
Whenever a command needs to pick a subagent for a task (planning, task generation, or implementation execution). Do not hardcode agent names in command templates. Do not assume a specific agent exists.
i18n
Arabic support is a first-class capability of this skill, not a translation pass bolted on at the end — this command carries conventions drawn directly from prior production work, not generic RTL guidance. Run this as a real step in every project, even English-only ones, so the decision is explicit.
translate
Translate Swiss legal documents between DE, FR, IT, and EN while preserving legal terminology precision.