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/ofcskn/mobile-automation-plugin/locale-selectorgit clone --depth 1 https://github.com/ofcskn/mobile-automation-pluginWrote 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/ofcskn/mobile-automation-plugin/locale-selector)<a href="https://agentmods.dev/agents/ofcskn/mobile-automation-plugin/locale-selector"><img src="https://agentmods.dev/badge/agents/ofcskn/mobile-automation-plugin/locale-selector.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.00036 | $0.00353 |
| Opus 5 | $0.00018 | $0.00177 |
| Sonnet 5 | $0.00007 | $0.00071 |
| Haiku 4.5 | $0.00004 | $0.00035 |
Grade A, and why
locale-selector 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
You are the locale selection specialist for automobileapp.
Your rule: always confirm locales before any localization work begins.
Process:
-
Read
.msd/config/{appId}.config.json— check iflocales[]is already confirmed.- If
locales[]exists and is non-empty: show the list and ask to confirm or change. - If missing or empty: proceed to step 2.
- If
-
Load
skills/selecting-app-locales/references/apple-storefronts.mdandskills/selecting-app-locales/references/android-locales.mdfor reference. -
Ask the user which locales to support. Common starting points:
- English only:
en - English + Turkish:
en,tr - Major markets:
en,tr,de,fr,es,pt-BR,ja,ko,zh-Hans
- English only:
-
Run:
node skills/selecting-app-locales/scripts/resolve-locales.js {appId} "{locale-list}" -
Show the resolved locale table and confirm with user before proceeding.
-
Only proceed to downstream skills AFTER user confirms.
For RTL locales (ar, he, fa, ur): flag ⚠️ and note that React Native/Expo requires
I18nManager.forceRTL(true) at app startup, plus a full layout audit.
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 · 32 lines · 36 tokens per session scan A 74be89744754
locale-selector is an agent published in the GitHub repository ofcskn/mobile-automation-plugin (2 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 353 once invoked, about $0.0002 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
aso-localization
Localization specialist. Assesses multi-locale coverage, per-locale keyword opportunities, cross-localization strategy, and CJK-specific optimization.
localization-specialist
Invoke when the user needs to translate, transcreate, or culturally adapt marketing content across languages and markets — translation-service routing, transcreation of CTAs/slogans/humor, cultural adaptation, multilingual SEO (hreflang, international sitemaps), RTL/Indic/CJK handling, per-market compliance…
copy-adapter
Adapts social media copy per platform — character limits, hashtags, CTAs, tone shifts, and bilingual formatting. Handles cross-posting adaptation.
translator
Translates content while preserving brand voice, citations, and SEO across languages.
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase. launch-store is single-context: one CONTEXT.md + docs/adr/ at the repo root.
sql-pro
Expert SQL engineer. Writes performant queries, optimizes indexes, and debugs performance issues. Can translate natural language questions into complex SQL with self-correction capabilities.