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 agentmods add skills/markdavidgan/apple-dev-skills/app-launchnpx skills add markdavidgan/apple-dev-skills --skill app-launchgit clone --depth 1 https://github.com/markdavidgan/apple-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/markdavidgan/apple-dev-skills/app-launch)<a href="https://agentmods.dev/skills/markdavidgan/apple-dev-skills/app-launch"><img src="https://agentmods.dev/badge/skills/markdavidgan/apple-dev-skills/app-launch.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 | $0.00085 | $0.03556 |
| Opus 5 | $0.00043 | $0.01778 |
| Sonnet 5 | $0.00017 | $0.00711 |
| Haiku 4.5 | $0.00009 | $0.00356 |
Grade A, and why
app-launch 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 4d 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 — 381 lines — stays where its author put it; the contents beside it link to each section on GitHub.
App Launch
Ship a new app or major version with a disciplined 8-week countdown — from final positioning to post-launch phased rollout.
This skill owns the end-to-end launch process. It delegates asset work to app-brand-identity, listing copy to asc-aso, submission mechanics to asc-submission, risk checks to submission-preflight, pricing to app-store-pricing, featuring pursuit to app-store-featured, build health to asc-build-check, and paid acquisition to apple-search-ads.
The 8-Week Launch Countdown
Week 8 — Lock Positioning
Goal: Nail the single sentence that explains why your app exists.
- Write the positioning statement: "For [audience] who [need], [App] is the [category] that [key differentiator]. Unlike [alternatives], we [unique proof point]."
- Confirm your monetization model and price tier — see
app-store-pricing - Define the one launch metric that declares success (downloads, revenue, rating count)
- Identify your 3–5 target keywords (seed for
asc-asolater) - Decide your release type: full release or phased? (See Release Strategy)
Week 7 — Brand and Store Assets
Goal: Hand off all visual deliverables so nothing blocks the listing later.
- App icon finalized at 1024×1024 px — hand off to
app-brand-identity - Screenshots designed for every required device size (iPhone 6.9", 6.5", iPad 13")
- App Preview video scripted and recorded (optional but strongly recommended for featuring)
- Feature graphic / promotional image ready
- Press kit: icon (1024px), screenshots (3 hero), brief (150 words), founder photo
Screenshots convert. Spend disproportionate time here. Lead with the emotional outcome, not the interface. Show text large enough to read on a phone-sized thumbnail in search results.
Week 6 — TestFlight Beta
Goal: Real signal from real people before GA.
Set up the beta group via ASC MCP
1. asc_list_apps → get your app ID
2. asc_create_beta_group → create "External Beta – Week 6" (external, requires review)
3. asc_set_beta_notes → set "What to Test" focus areas
4. asc_invite_beta_tester → add testers by email (up to 10,000 external)
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.
- 4d ago First seen · 381 lines · 85 tokens per session scan A efaebe1c6a89
app-launch is a skill published in the GitHub repository markdavidgan/apple-dev-skills (5 stars, last pushed 5d ago), licensed MIT. It adds 85 tokens to every session and 3,556 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
asc-revenuecat-catalog-sync
Reconcile App Store Connect subscriptions and in-app purchases with RevenueCat products, entitlements, offerings, and packages using asc and RevenueCat MCP. Use when setting up or syncing subscription catalogs across ASC and RevenueCat.
asc-localize-metadata
Automatically translate and sync App Store metadata (description, keywords, what's new, subtitle) to multiple languages using LLM translation and asc CLI. Use when asked to localize an app's App Store listing, translate app descriptions, or add new languages to App Store Connect.
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…
asc-metadata-sync
Sync, validate, and apply App Store metadata with the current asc canonical metadata workflow. Use when updating metadata, localizations, keywords, or migrating legacy fastlane metadata.
asc-release-flow
Orchestrate App Store releases with asc, including staging a version, uploading or building an artifact, publishing, and submitting for review. Use when the user wants to prepare or execute a release. Keep Game Center item preparation in this skill; route other readiness failures, stuck submissions, cancellation, and…
asc-submission-health
Diagnose App Store submission blockers and operate review health with asc, including readiness validation, repair routing, status monitoring, cancellation, and retry decisions. Use when validation fails, a version is not in a valid state, review status is unclear or stuck, or a failed submission must be repaired and…