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 scoregit 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/score)<a href="https://agentmods.dev/skills/vishalvshekkar/app-store-toolkit/score"><img src="https://agentmods.dev/badge/skills/vishalvshekkar/app-store-toolkit/score.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.00021 | $0.00735 |
| Opus 5 | $0.00010 | $0.00367 |
| Sonnet 5 | $0.00004 | $0.00147 |
| Haiku 4.5 | $0.00002 | $0.00073 |
Grade A, and why
app-store-toolkit:score 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 7d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/app-store-toolkit:score
You are scoring the ASO quality of the app's metadata and providing actionable improvement suggestions.
Steps
1. Load All Metadata
Call store_read_config and then read all metadata for the target locale (primary if not specified):
- name, subtitle, keywords (app-level)
- description, promotional_text (per platform)
If no config exists, tell the user: "Run /app-store-toolkit:setup first to configure your app." and STOP.
2. Score Each Category (0-100)
Calculate scores across these dimensions:
Keyword Optimization (25 points):
- Keywords field fully utilized (close to 100 chars)? [10 pts]
- No duplicate words across name + subtitle + keywords? [5 pts]
- Keywords are relevant and specific (not too broad)? [5 pts]
- Singular forms used (no plurals that waste chars)? [5 pts]
Name & Subtitle Quality (20 points):
- Name includes primary keyword? [5 pts]
- Name is memorable/brandable? [5 pts]
- Subtitle adds unique value (not repeating name)? [5 pts]
- Both near (but within) character limits? [5 pts]
Description Quality (25 points):
- First 3 lines are compelling (pre-"Read More")? [8 pts]
- Uses bullet points or scannable formatting? [4 pts]
- Includes keywords naturally? [5 pts]
- Has clear call to action? [4 pts]
- Good length (1000+ chars for depth, under 4000)? [4 pts]
Completeness (15 points):
- All fields populated? [5 pts]
- Promotional text set? [5 pts]
- Release notes present? [5 pts]
Localization Coverage (15 points):
- Number of locales configured vs recommended? [8 pts]
- All locales have complete metadata? [7 pts]
3. Present Score
ASO Score: 73/100
═══════════════════════════════════════════
Keyword Optimization: 18/25
Name & Subtitle: 16/20
Description Quality: 19/25
Completeness: 12/15
Localization Coverage: 8/15
═══════════════════════════════════════════
Top Improvements:
1. Keywords field is only 67/100 chars — add more relevant terms (+5 pts)
2. Missing localizations: ja, de-DE, fr-FR are high-value markets (+4 pts)
3. Description lacks bullet points for scanability (+3 pts)
4. Subtitle repeats words from name — use different keywords (+2 pts)
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.
- 7d ago First seen · 93 lines · 21 tokens per session scan A 2c1805ea5a5c
app-store-toolkit:score is a skill published in the GitHub repository vishalvshekkar/app-store-toolkit (5 stars, last pushed 3mo ago), licensed MIT. It adds 21 tokens to every session and 735 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…
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…