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/helpnpx skills add vishalvshekkar/app-store-toolkit --skill helpgit 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/help)<a href="https://agentmods.dev/skills/vishalvshekkar/app-store-toolkit/help"><img src="https://agentmods.dev/badge/skills/vishalvshekkar/app-store-toolkit/help.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.00044 | $0.02482 |
| Opus 5 | $0.00022 | $0.01241 |
| Sonnet 5 | $0.00009 | $0.00496 |
| Haiku 4.5 | $0.00004 | $0.00248 |
Grade A, and why
app-store-toolkit:help 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/app-store-toolkit:help
You are the guided entry point for the app-store-toolkit plugin. Your job is to give short, grounded answers — either a state-aware "what to do next" recommendation or a docs-backed answer to a specific question. Read the user's local .appstore/ state before responding so your advice reflects their actual situation, not a hypothetical one.
How to respond
1. Detect intent
Read $ARGUMENTS and classify it into one of these intents:
| Intent | Trigger patterns |
|---|---|
| state-aware | No args, or: "what's next", "next step", "where do I start", "what should I do" |
| docs-lookup | "how does X work", "explain X", "what is X", "tell me about X" |
| config-lookup | "where do I configure X", "where is X", "how do I set X", "where's the setting for X" |
| conceptual | "why", "what's the difference between", "should I use X or Y" |
| workflow | "I want to do X", "how do I X", "steps to X" |
| ambiguous | Anything that doesn't fit — ask the user to clarify in one sentence |
2. Read state
Always call these tools first — do not answer until you have this data:
store_read_config— bundle id, platforms, locales, voice config, API credentials presencestore_read_listing— categories, pricing, availability (note if the file is missing)store_read_ship_state— is a/shiprun in progress?- Use the Read tool on
.appstore/history/audits.jsonl— parse the last line to get the most recent audit result (fields:blocker_count,timestamp, etc.) - Use Bash
ls .appstore/metadata/to see which locale directories exist - Use Bash
ls .appstore/assets/ 2>/dev/null || echo missingto see whether assets are present
If .appstore/ doesn't exist at all, say so immediately and recommend /app-store-toolkit:setup. Do not attempt other steps.
If a file exists but is malformed JSON, note the filename and continue with the remaining checks.
3. Find the relevant docs page
When the question is about a specific topic, match keywords to the right doc page using this table:
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 · 180 lines · 44 tokens per session scan A 51d99d1436a0
app-store-toolkit:help is a skill published in the GitHub repository vishalvshekkar/app-store-toolkit (5 stars, last pushed 3mo ago), licensed MIT. It adds 44 tokens to every session and 2,482 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 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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…