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 mtbun/storeshots-mcp --skill storeshotsgit clone --depth 1 https://github.com/mtbun/storeshots-mcpWrote 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/mtbun/storeshots-mcp/storeshots)<a href="https://agentmods.dev/skills/mtbun/storeshots-mcp/storeshots"><img src="https://agentmods.dev/badge/skills/mtbun/storeshots-mcp/storeshots/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/mtbun/storeshots-mcp/storeshots"><img src="https://agentmods.dev/badge/skills/mtbun/storeshots-mcp/storeshots.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.00078 | $0.01180 |
| Opus 5.5 | $0.00031 | $0.00472 |
| Sonnet 5.5 | $0.00016 | $0.00236 |
| Haiku 4.5 | $0.00008 | $0.00118 |
Grade A, and why
storeshots 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 10d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
storeshots — guided store screenshot workflow
Produce a complete, consistent set of store-ready marketing screenshots for an app, using the storeshots rendering tools. You do the thinking (benefits, copy, translation); the tools do the pixels.
Tooling check
If the project already has a storeshots.json, it is the source of truth: edit it and run storeshots build, skipping the setup phases. Only the files whose inputs changed are re-rendered.
Use the CLI: npx -y --package=storeshots-mcp storeshots <command> (or storeshots if it is installed globally). The whole listing lives in one storeshots.json, and storeshots build renders it, re-rendering only what changed. Run storeshots build --help to see the config format. If there is no shell but the storeshots MCP server is connected, call build_project with the config path instead; it runs the same engine. Add --json to any command when you need to parse its output. Exit code 2 means bad usage or config, and the output lists every problem with its path.
Phase 1 — Configuration
Ask the user, as a short checklist:
- Platforms: which presets? Offer ios-phone, android-phone, ipad-13, android-tablet, play-feature-graphic. Default: ios-phone + android-phone.
- Count: how many screenshots per platform? Default 6, max 10.
- Language(s): default English first, then translate. Note the BCP-47 codes; they control locale-correct uppercasing.
- Brand color: 6-digit hex. If a codebase is available, look for the primary/theme color and propose it instead of asking cold.
- Screenshots source: existing image files (collect paths), or guide the user through capturing simulator/emulator screenshots first. If iOS and Android captures differ, or the UI is localized, use path templates such as
shots/{platform}/{lang}/home.png.
Then run storeshots init --screens <dir> --presets <ids> --langs <codes> --bg <hex>. It writes storeshots.json with one screen per image and TODO headlines.
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.
- 10d ago First seen · 57 lines · 78 tokens per session scan A 6dbfd8bcff42
storeshots is a skill published in the GitHub repository mtbun/storeshots-mcp (26 stars, last pushed 9d ago), licensed MIT. It adds 78 tokens to every session and 1,180 once invoked, about $0.0003 per session on Opus 5.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-10-11.
Other skills, from other repositories
aso-playbook
Beginner-friendly App Store Optimization guide covering keyword research, screenshot design, rating management, and A/B testing for iOS and Android. By @WeiYipei — practical ASO for indie developers and small teams.
localization-strategy
Localization and internationalization strategy for iOS/macOS apps. Covers market prioritization, language tier recommendations, minimum viable localization levels, translation workflows, cultural adaptation, localized ASO, and testing. Use when planning localization, expanding to new markets, deciding which languages…
iap-finalizer
Take a one-time in-app purchase from MISSINGMETADATA to READYTOSUBMIT in App Store Connect — set its price schedule and localized display name/description (and optional review screenshot) via the ASC REST API. Use at Phase 6 (Pre-Release), after the IAP is built in-app (Phase 4) and its ASC record exists. NOT for…
localization-setup
Generate internationalization (i18n) infrastructure for multi-language support in iOS/macOS apps. Use when localizing for multiple languages, adopting String Catalogs (xcstrings), or supporting RTL languages.
gingiris-aso-growth
A broad guide to growing mobile apps through App Store Optimization, launch planning, creator-made content, and marketing on platforms such as TikTok, Instagram, and YouTube Shorts.
gr-aso
A skill for app-store optimization, or improving how an app is found and presented in the App Store and Google Play, plus launch planning for a new app. It covers listing text, screenshots and video, ratings, creator content, advertising, and localization.