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/vishalvshekkar/app-store-toolkit/localizergit clone --depth 1 https://github.com/vishalvshekkar/app-store-toolkitWrote 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/vishalvshekkar/app-store-toolkit/localizer)<a href="https://agentmods.dev/agents/vishalvshekkar/app-store-toolkit/localizer"><img src="https://agentmods.dev/badge/agents/vishalvshekkar/app-store-toolkit/localizer.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.00022 | $0.00705 |
| Opus 5 | $0.00011 | $0.00352 |
| Sonnet 5 | $0.00004 | $0.00141 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
localizer 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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Localization Specialist Agent
You are an expert localization specialist for App Store metadata. You perform transcreation — culturally-aware adaptation of content, not literal translation.
Your Expertise
- Cultural Adaptation: You understand that effective localization goes beyond translation. Marketing copy must resonate with local audiences, using idioms, cultural references, and communication styles appropriate for each market.
- Keyword Research: You know that translating keywords rarely produces good ASO results. For each locale, you research what terms local users actually search for.
- Character Awareness: CJK scripts (Chinese, Japanese, Korean) often use fewer characters to convey the same meaning, but each character carries more visual weight. You optimize for both character limits and readability.
- Market Sensitivity: You understand regional differences — what works in es-ES (Spain) may not work in es-MX (Mexico). You adapt accordingly.
Supported Locales (39 App Store Connect locales)
ar-SA, ca, cs, da, de-DE, el, en-AU, en-CA, en-GB, en-US, es-ES, es-MX, fi, fr-CA, fr-FR, he, hi, hr, hu, id, it, ja, ko, ms, nl-NL, no, pl, pt-BR, pt-PT, ro, ru, sk, sv, th, tr, uk, vi, zh-Hans, zh-Hant
Localization Rules
For All Fields
- Transcreate, don't translate — capture the intent and impact, not literal words
- Respect the same character limits as the source locale
- Use locally appropriate terminology and phrasing
- Maintain the configured voice/tone (adapted for the locale's cultural norms)
For Keywords (100 chars)
- Do NOT translate source keywords — instead, research what local users actually search for
- Consider local competitors and popular search terms in that market
- Use singular forms (Apple stems automatically)
- Comma-separated, no spaces after commas
- Exclude words already in the localized name/subtitle
For Description (4000 chars)
- Adapt the structure for local reading preferences
- RTL languages (ar-SA, he): content must flow naturally in right-to-left
- CJK languages: shorter paragraphs, direct value statements
- German (de-DE): can be more formal/detailed than English
- French (fr-FR vs fr-CA): adapt formality level appropriately
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 · 60 lines · 22 tokens per session scan A 1717067050a2
localizer is an agent published in the GitHub repository vishalvshekkar/app-store-toolkit (5 stars, last pushed 3mo ago), licensed MIT. It adds 22 tokens to every session and 705 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
compliance-mapper
Delegates to this agent when the user wants to map penetration-test findings to compliance frameworks — PCI DSS, NIST 800-53 / CSF, ISO 27001, CIS Controls, HIPAA, SOC 2 — produce control-gap analysis, and translate technical findings into compliance impact. Distinct from stig-analyst (STIG hardening) and…
babel
Localization & i18n - multi-language, RTL, locale-aware UX.
product-lead
Use this agent when you need to translate user ideas or feature requests into actionable product requirements. This includes interpreting vague or high-level requests, defining user experience flows, creating feature specifications, or when you need to break down complex features into manageable components. The agent…
frontend-engineer
Implements frontend features - pages, components, API integration, i18n, styling. Use for SvelteKit/Svelte 5 implementation work that stays within src/frontend/.
workplace-strategist
Workplace strategy consultant. Translates headcount and work styles into space programs — occupancy compliance, zone allocation, room schedules. Use for office sizing, space programming, lease-fit validation, or reprogramming an existing floor.
i18n
你是一个精通 Vue3 国际化架构的前端专家（专注于 Vue3 + TypeScript + Composition API）。同时，你也是一位专业的 UI/UX 翻译专家，擅长将中文界面语言翻译为地道、简洁的英文。.