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 skills add vishalvshekkar/app-store-toolkit --skill localizegit 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/skills/vishalvshekkar/app-store-toolkit/localize)<a href="https://agentmods.dev/skills/vishalvshekkar/app-store-toolkit/localize"><img src="https://agentmods.dev/badge/skills/vishalvshekkar/app-store-toolkit/localize.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.1 | $0.00018 | $0.00895 |
| Opus 5 | $0.00009 | $0.00447 |
| Sonnet 5 | $0.00004 | $0.00179 |
| Haiku 4.5 | $0.00002 | $0.00089 |
Grade A, and why
app-store-toolkit:localize 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 6d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/app-store-toolkit:localize
You are localizing App Store metadata into target locales. Use the Localization Specialist agent persona from agents/localizer.md.
Steps
1. Load Configuration
Call store_read_config to get:
- Primary locale (source for translations)
- Configured locales (targets)
- Voice/tone settings
- Platforms
If no config exists, tell the user: "Run /app-store-toolkit:setup first to configure your app." and STOP.
2. Determine Targets
- If
$ARGUMENTSspecifies a locale, only localize to that locale - If
$ARGUMENTSspecifies a field, only localize that field - Otherwise, localize all fields to all non-primary locales
3. Load Source Content
Read all metadata in the primary locale:
store_read_metadatafor name, subtitle, keywordsstore_read_metadatafor description, promotional_text (per platform)
If the primary locale has no content for a field, skip it and warn the user.
4. Localize Each Target Locale
For EACH target locale, for EACH field:
Apply the Localization Specialist agent approach:
- Transcreate (not literal translate) the content
- For keywords: research locale-specific keywords rather than translating
- Adapt voice/tone for the locale's cultural expectations
- Stay within character limits
Character Limits (same as source):
| Field | Limit |
|---|---|
| Name | 30 |
| Subtitle | 30 |
| Keywords | 100 |
| Promotional Text | 170 |
| Description | 4000 |
| Release Notes | 4000 |
| IAP Display Name | 30 |
| IAP Description | 45 |
5. Validate Each Localization
After generating each localized field, validate against character limits. If exceeded, regenerate with explicit constraint (up to 2 retries).
6. Present Results
Show a locale-by-locale summary:
Localization Results:
═════════════════════════════════════════
Target: ja (Japanese)
name: "マイアプリ" (5/30 chars)
subtitle: "素早くクールに" (7/30 chars)
keywords: "生産性,タスク,整理,計画..." (82/100 chars)
description: 2156/4000 chars
promotional_text: 28/170 chars
Target: de-DE (German)
name: "Meine App" (9/30 chars)
subtitle: "Dinge schneller erledigen" (25/30 chars)
keywords: "produktivität,aufgaben,organisieren..." (91/100 chars)
description: 2879/4000 chars
promotional_text: 45/170 chars
═════════════════════════════════════════
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.
- 6d ago First seen · 117 lines · 18 tokens per session scan A 15c95dcf4a3d
app-store-toolkit:localize is a skill published in the GitHub repository vishalvshekkar/app-store-toolkit (5 stars, last pushed 3mo ago), licensed MIT. It adds 18 tokens to every session and 895 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 skills, from other repositories
chinese-documentation
A Chinese technical-documentation style guide covering spacing, punctuation, numbers, terminology, and links when Chinese and English appear together.
azure-ai-translation-text-py
Azure AI Text Translation SDK for real-time text translation, transliteration, language detection, and dictionary lookup. Use for translating text content in applications. Triggers: "text translation", "translator", "translate text", "transliterate", "TextTranslationClient".
harden
Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready. Use when the user asks to harden, make production-ready, handle edge cases, add error states, or fix overflow and i18n issues.
seedance-vocab-ja
This skill should be used when the user asks for Japanese Seedance 2.0 prompt wording, Japanese cinematic vocabulary, or translation of camera, lighting, action, VFX, audio, and production terms into Japanese.
asc-subscription-localization
Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work.
tiktok-shop-cross-border
Cross-border selling on TikTok Shop. Market selection, logistics setup, localization strategy, compliance requirements, and international expansion. Use when the user asks about TikTok Shop international selling, cross-border ecommerce, global expansion, or selling in multiple countries.