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 JasonColapietro/ios-app-dev-skills --skill ios-screenshot-takergit clone --depth 1 https://github.com/JasonColapietro/ios-app-dev-skillsWrote 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/jasoncolapietro/ios-app-dev-skills/ios-screenshot-taker)<a href="https://agentmods.dev/skills/jasoncolapietro/ios-app-dev-skills/ios-screenshot-taker"><img src="https://agentmods.dev/badge/skills/jasoncolapietro/ios-app-dev-skills/ios-screenshot-taker/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/jasoncolapietro/ios-app-dev-skills/ios-screenshot-taker"><img src="https://agentmods.dev/badge/skills/jasoncolapietro/ios-app-dev-skills/ios-screenshot-taker.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.00543 |
| Opus 5 | $0.00039 | $0.00271 |
| Sonnet 5 | $0.00016 | $0.00109 |
| Haiku 4.5 | $0.00008 | $0.00054 |
Grade A, and why
ios-screenshot-taker 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 11d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iOS Screenshot Taker
Principle
Capture real app states, not imagined UI. The screenshot set should be repeatable from a clean simulator and should map each image to a named product state, device class, locale, and store-listing purpose.
Workflow
- Identify the Xcode project or workspace, scheme, bundle ID, simulator device, app version, build number, and target screenshot states.
- Confirm the app can launch with deterministic demo data or safe seeded state.
- Run
scripts/take_ios_screenshots.shfrom this repository when available, or follow the samexcodebuildandxcrun simctlsequence manually. - Capture one named PNG per app state and keep filenames sortable.
- Hand the raw captures to
ios-aso-launchor the app-store screenshot editor for marketing framing, captions, and required export sizes.
Read references/screenshot-runbook.md before doing non-trivial capture work.
State Contract
Prefer launch arguments that the app can recognize, for example:
--ui-testing --screenshot-state home
--ui-testing --screenshot-state detail
--ui-testing --screenshot-state paywall
If the app has no screenshot-state router, use the safest available path: seed local demo data, launch the app, navigate manually once, then document any manual steps in the output.
Public-Safe Defaults
- Do not capture private user accounts, unreleased customer data, tokens, API keys, internal dashboards, private App Store Connect screens, or support contact details.
- Do not commit oversized raw screenshot folders unless the repository is meant to store release assets.
- Downscale README/showcase images and keep the original store-resolution files in the app release folder.
- Do not claim App Store approval from screenshot files alone; verify live Apple lookup or App Store Connect state separately.
Required Output
Report:
- capture command used,
- simulator device and iOS runtime,
- app path or bundle ID,
- output directory,
- screenshot files produced,
- missing states or manual steps,
- whether the captures are raw QA screenshots or framed store assets.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 64 lines · 78 tokens per session scan A 4fc50d338d29
ios-screenshot-taker is a skill published in the GitHub repository JasonColapietro/ios-app-dev-skills (3 stars, last pushed 4d ago), licensed MIT. It adds 78 tokens to every session and 543 once invoked, about $0.0004 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
beta-testing
Beta testing strategy for iOS/macOS apps. Covers TestFlight program setup, beta tester recruitment, feedback collection methodology, user interviews, signal-vs-noise interpretation, and go/no-go launch readiness decisions. Use when planning a beta, setting up TestFlight, collecting user feedback, or deciding if ready…
accessibility-audit
Run a structured accessibility audit on an iOS/macOS app — automated XCUITest audits, Accessibility Inspector, manual VoiceOver/Dynamic Type passes, and App Store Accessibility Nutrition Label evaluation. Use before release, when preparing Nutrition Label declarations, or for EU Accessibility Act compliance.
asc-shots-pipeline
Orchestrate iOS screenshot automation with xcodebuild/simctl for build-run, AXe for UI actions, JSON settings and plan files, Koubou-based framing (asc screenshots frame), and screenshot upload (asc screenshots upload). Use when users ask for automated screenshot capture, AXe-driven simulator flows, frame composition…
app-rejection-recovery
When the user's app or update was rejected by Apple App Review or Google Play Review and they need to diagnose why, fix it, and resubmit fast. Use when the user mentions "app rejected", "App Review rejection", "guideline violation", "Apple rejected my app", "Google Play rejected", "Play policy violation", "Resolution…
apple-search-ads
When the user wants to set up, optimize, or scale Apple Search Ads (ASA) campaigns — including keyword bidding, match types, campaign structure, Creative Product Sets, CPP routing, and ROAS optimization. Use when the user mentions "Apple Search Ads", "ASA", "Search Ads", "Search tab ads", "Today tab ads", "CPT"…
attribution-setup
When the user wants to set up, debug, or interpret app install attribution — including SKAdNetwork (SKAN), Apple's AdAttributionKit, Google Play Install Referrer, MMPs (AppsFlyer, Adjust, Singular, Branch, Kochava), deep links, deferred deep links, conversion values, postback windows, or privacy thresholds. Use when…