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 markdavidgan/apple-dev-skills --skill apple-routergit 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/apple-router)<a href="https://agentmods.dev/skills/markdavidgan/apple-dev-skills/apple-router"><img src="https://agentmods.dev/badge/skills/markdavidgan/apple-dev-skills/apple-router.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.00100 | $0.01331 |
| Opus 5 | $0.00050 | $0.00665 |
| Sonnet 5 | $0.00020 | $0.00266 |
| Haiku 4.5 | $0.00010 | $0.00133 |
Grade A, and why
apple-router 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.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apple Router
Turn a fuzzy goal into the right skill, in the right order. When a request is broad ("grow my app", "get ready to launch", "why is revenue flat"), don't guess — map the goal to the lifecycle stage, hand off to the specific skill(s), and sequence them. This skill routes; the named skills do the work.
If the request already names a clear task (e.g. "audit my keywords", "fix this rejection"), skip the router and go straight to that skill. Use this only to disambiguate.
How to route
- Classify the intent into a stage (table below).
- If foundational context is missing, run the foundation skill first:
app-marketing-contextfor any growth/marketing work,product-specfor a feature. - Dispatch to the matched skill(s).
- If the goal spans stages, run them in the order given and tell the user the sequence up front.
Intent → skill map
Discovery & growth ("more installs", "rank higher", "grow")
| The user wants… | Route to |
|---|---|
| Set up reusable marketing context first | app-marketing-context (do this before the rest) |
| Rank for more / better keywords, audit the listing | asc-aso |
| Run paid acquisition on the App Store | apple-search-ads |
| Plan a launch or major-version release | app-launch |
| Get featured by Apple editors | app-store-featured |
| Brand, icon, screenshots, marketing assets | app-brand-identity → app-icon-composer |
Conversion & money ("more revenue", "improve the paywall")
| The user wants… | Route to |
|---|---|
| Design / fix the paywall | paywall-design |
| Set or restructure pricing | app-store-pricing |
| Implement purchases in code | storekit-purchases |
| Manage the subscriber journey (trials, churn, win-back) | subscription-lifecycle |
Activation & retention ("users drop off", "keep users")
| The user wants… | Route to |
|---|---|
| Fix the first-run / onboarding flow | onboarding-optimization |
| Improve D1/D7/D30 retention | retention-optimization |
| Decide what to measure | app-analytics |
| Get more / better ratings | rating-prompt-strategy |
| Respond to and learn from reviews | review-management |
| Re-engage with notifications | push-notifications |
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 · 96 lines · 100 tokens per session scan A 5f08d678351b
apple-router is a skill published in the GitHub repository markdavidgan/apple-dev-skills (5 stars, last pushed 9d ago), licensed MIT. It adds 100 tokens to every session and 1,331 once invoked, about $0.0005 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…