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 skills/vishalvshekkar/app-store-toolkit/validatenpx skills add vishalvshekkar/app-store-toolkit --skill validategit 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/validate)<a href="https://agentmods.dev/skills/vishalvshekkar/app-store-toolkit/validate"><img src="https://agentmods.dev/badge/skills/vishalvshekkar/app-store-toolkit/validate.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.00014 | $0.00804 |
| Opus 5 | $0.00007 | $0.00402 |
| Sonnet 5 | $0.00003 | $0.00161 |
| Haiku 4.5 | $0.00001 | $0.00080 |
Grade A, and why
app-store-toolkit:validate 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 5d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/app-store-toolkit:validate
You are validating App Store metadata against Apple's character limits.
Character Limits Reference
| Field | Limit | Level |
|---|---|---|
| App Name | 30 | App-level |
| Subtitle | 30 | App-level |
| Keywords | 100 | Version-level |
| Promotional Text | 170 | Version-level |
| Description | 4000 | Version-level |
| What's New | 4000 | Version-level |
| IAP Display Name | 30 | IAP-level |
| IAP Description | 45 | IAP-level |
Steps
1. Read Config
Call store_read_config to get the configured locales and platforms.
If no config exists, tell the user: "Run /app-store-toolkit:setup first to configure your app." and STOP.
2. Run Validation
Call store_validate with any locale/platform filters from $ARGUMENTS.
3. Present Results
Format results clearly. For each field:
- Show the field name, locale, and platform (if applicable)
- Show current length vs limit
- Mark as PASS or FAIL
Example output:
Validation Results for en-US (ios)
═══════════════════════════════════════════════
PASS name 14 / 30 chars
PASS subtitle 21 / 30 chars
PASS keywords 87 / 100 chars
PASS description 2341 / 4000 chars
FAIL promotional_text 185 / 170 chars (+15 over)
═══════════════════════════════════════════════
Result: 1 of 5 fields exceed limits
4. Suggest Fixes
For any FAIL results:
- Show the current content
- Suggest running
/app-store-toolkit:asoto regenerate with proper constraints - For minor overages (< 10 chars), suggest specific edits to trim
5. Multi-Locale Summary
If validating multiple locales, show a summary table:
Locale | Fields | Pass | Fail
────────────────────────────────
en-US | 5 | 4 | 1
ja | 5 | 5 | 0
de-DE | 5 | 3 | 2
Asset dimension validation
If .appstore/assets/{platform}/ exists, run:
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.
- 5d ago First seen · 100 lines · 14 tokens per session scan A 1626bab5f473
app-store-toolkit:validate is a skill published in the GitHub repository vishalvshekkar/app-store-toolkit (5 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 804 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…