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 render-screenshotsgit 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/render-screenshots)<a href="https://agentmods.dev/skills/vishalvshekkar/app-store-toolkit/render-screenshots"><img src="https://agentmods.dev/badge/skills/vishalvshekkar/app-store-toolkit/render-screenshots.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.00036 | $0.00415 |
| Opus 5 | $0.00018 | $0.00208 |
| Sonnet 5 | $0.00007 | $0.00083 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
app-store-toolkit:render-screenshots 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 8d 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.
What it actually says
/app-store-toolkit:render-screenshots
Render template-based screenshots using the bundled Puppeteer renderer.
Steps
1. Verify templates exist
Check .appstore/templates/ for screenshot-{device}.html files. If none, tell the user to run /app-store-toolkit:setup and accept the starter templates, or to add their own.
2. Verify assets.json has entries
For each locale × device in scope, read .appstore/metadata/{locale}/{platform}/assets.json. If screenshots[{device}] is empty or missing, skip that combination and warn.
3. Render
For each locale × device with entries and a template:
- Call
assets_render_template({ locale, platform: "ios", device }). - The first call triggers a Chromium download (~280 MB). Print a one-time notice telling the user this is happening.
- The tool writes PNGs to
.appstore/assets/ios/{locale}/{device}/screenshots/.
4. Suggest next steps
Rendered 36 screenshots across 9 locales × 4 devices.
Run /app-store-toolkit:validate to confirm dimensions, then /app-store-toolkit:push --assets.
Suggested next
/app-store-toolkit:validate— confirm rendered screenshots meet Apple's required dimensions/app-store-toolkit:push— upload the validated screenshots to App Store Connect- See also: docs/workflows/assets-pipeline.md
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.
- 8d ago First seen · 48 lines · 36 tokens per session scan A 0579d49fc103
app-store-toolkit:render-screenshots is a skill published in the GitHub repository vishalvshekkar/app-store-toolkit (5 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 415 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
feature-demo-recording
Record a demo video of a web feature from a real browser. Two modes -- a NARRATED film where measured voiceover drives the timeline (designed slides, subtitles, punch-in camera, rendered from an HTML timeline), and a SILENT evidence clip for a PR or a QA pass. Use when the user asks to record a video, demo, or screen…
browser-video-recording
Create polished 60 fps 4:3 4K browser screen-recording style videos from Codex in-app browser captures, with browser-only crop, natural macOS cursor styling, deliberate click choreography, zoom-follow framing, ffprobe/thumbnail verification, and optional native recording compatibility checks. Use when the user asks to…
html-to-video-pipeline
Reliable HTML-to-MP4 rendering via headless browser recording (Playwright/Puppeteer) + ffmpeg — the ordering, gotchas, and verification steps you MUST get right or the output silently rots. Trigger whenever the user is building or debugging any pipeline that turns an HTML/CSS/JS page (single-file, multi-composition…
record-video
Record and upload a short browser interaction video artifact.
playwright-recording
Record browser interactions as video using Playwright. Use for capturing demo videos, app walkthroughs, and UI flows for Remotion videos. Triggers include recording a demo, capturing browser video, screen recording a website, or creating walkthrough footage.
playwright-recording
Record browser interactions as video using Playwright. Use for capturing demo videos, app walkthroughs, and UI flows for Remotion videos. Triggers include recording a demo, capturing browser video, screen recording a website, or creating walkthrough footage.