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 reviewsgit 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/reviews)<a href="https://agentmods.dev/skills/vishalvshekkar/app-store-toolkit/reviews"><img src="https://agentmods.dev/badge/skills/vishalvshekkar/app-store-toolkit/reviews/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/vishalvshekkar/app-store-toolkit/reviews"><img src="https://agentmods.dev/badge/skills/vishalvshekkar/app-store-toolkit/reviews.svg" alt="Reviewed on agentmods" width="80" 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.00013 | $0.00955 |
| Opus 5 | $0.00006 | $0.00477 |
| Sonnet 5 | $0.00003 | $0.00191 |
| Haiku 4.5 | $0.00001 | $0.00096 |
Grade A, and why
app-store-toolkit:reviews 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 9d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/app-store-toolkit:reviews
You are managing customer reviews from App Store Connect.
Steps
1. Load Configuration
Call store_read_config to get app_id and voice/tone settings.
If no app_id, tell the user to run /app-store-toolkit:setup and /app-store-toolkit:pull first.
2. Determine Action
Parse $ARGUMENTS:
list(default): Fetch and display reviewsrespond: Draft a response to a specific reviewanalyze: Provide insights across recent reviews
For list:
Call asc_get_reviews with:
app_idfrom configsort: Map user-friendly names → API values:- newest →
-createdDate - oldest →
createdDate - highest →
-rating - lowest →
rating
- newest →
limit: from args or default 20
Display reviews in a readable format:
Customer Reviews (20 most recent)
═══════════════════════════════════════
★★★★★ "Love this app!" — JohnD123 (US, Feb 2026)
Best productivity app I've found. The timer feature is perfect.
★★☆☆☆ "Crashes on iPad" — iPadUser (UK, Feb 2026)
App crashes every time I try to open settings on my iPad Pro.
★★★★☆ "Great but needs widgets" — WidgetFan (DE, Jan 2026)
Really enjoying the app, would love to see home screen widgets.
═══════════════════════════════════════
Average: 4.2 stars | Total shown: 20
For respond:
Ask the user which review to respond to (by ID or by selecting from the list).
Draft a response following these guidelines:
- Use the app's configured voice/tone
- Be professional and empathetic regardless of rating
- Address the specific feedback
- For bug reports: acknowledge the issue, mention it's being looked into
- For feature requests: thank them, note the suggestion
- For positive reviews: express gratitude, encourage sharing
- Keep responses concise (no character limit for responses, but shorter is better)
Show the draft and ask for approval before posting.
When approved, call asc_post_review_response with the review_id and response text.
For analyze:
Fetch recent reviews and provide insights:
- Rating distribution breakdown
- Common themes in positive reviews (what users love)
- Common complaints or feature requests
- Sentiment trends (improving/declining)
- Actionable suggestions based on feedback patterns
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.
- 9d ago First seen · 123 lines · 13 tokens per session scan A 832b937b3f99
app-store-toolkit:reviews is a skill published in the GitHub repository vishalvshekkar/app-store-toolkit (5 stars, last pushed 3mo ago), licensed MIT. It adds 13 tokens to every session and 955 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…
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…
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…