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 asc-auditgit 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/asc-audit)<a href="https://agentmods.dev/skills/markdavidgan/apple-dev-skills/asc-audit"><img src="https://agentmods.dev/badge/skills/markdavidgan/apple-dev-skills/asc-audit.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.00085 | $0.01817 |
| Opus 5 | $0.00043 | $0.00908 |
| Sonnet 5 | $0.00017 | $0.00363 |
| Haiku 4.5 | $0.00009 | $0.00182 |
Grade A, and why
asc-audit 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ASC Drift Audit
This skill answers one question: is what we believe still true?
It is not a rule checker and not a fixer. It diffs three sources of truth — live ASC, the repo, and what the project's launch/submission docs claim — and reports where they disagree. Every fix is a human decision, except an unambiguous doc correction (a stale fact restated to match live state) with no submission-strategy judgment involved — apply those, flag everything else.
asc_audit({
app_id: "<App Store Connect App ID, from asc_list_apps>",
repo_build: "<optional: expected build number from the repo>",
repo_version: "<optional: expected marketing version from the repo>",
runbook_path: "<optional: path to a canonical launch/state doc for freshness check>"
})
Why this exists
Two independent incidents, in two different apps, six weeks apart, found the same shape of silent drift:
| Drift | Silent for |
|---|---|
| A version's draft was attached to an old build while several newer builds shipped past it | ~6 days |
| Release-notes text identical across many builds (copied forward, not rewritten) | 8+ builds |
| A TestFlight feedback email pointing at a stale/wrong domain | unknown |
| A canonical "where we stand" doc presenting old state as current | 6 days |
A version actually REJECTED in ASC while the canonical doc still said WAITING_FOR_REVIEW |
3 days, 8 builds |
| Live ASC review notes naming a build number 8 versions stale, and missing a disclosure paragraph the local doc had | unknown, at least 8 builds |
None of these were knowledge gaps. The information needed to catch each
one was already sitting in a doc or a teammate's memory. The drift happened
anyway because every other ASC skill is a forward action — a ship skill
uploads, a beta-distribution skill attaches, submission-preflight runs once
at submission time. Nothing ever goes back and re-checks what's actually
true on Apple's servers right now. That is the gap this fills.
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 · 153 lines · 85 tokens per session scan A 6eef2c845106
asc-audit is a skill published in the GitHub repository markdavidgan/apple-dev-skills (5 stars, last pushed 9d ago), licensed MIT. It adds 85 tokens to every session and 1,817 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…