rorkai/app-store-connect-cli-skills is a community-maintained collection of Agent Skills for using the asc command-line tool with Apple App Store Connect and Apple Ads. It helps coding agents automate builds, TestFlight, metadata, submissions, signing, and advertising workflows.
Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/rorkai/app-store-connect-cli-skillsnpx agentmods add skills/rorkai/app-store-connect-cli-skills/asc-ad-hoc-distributionWrote 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/rorkai/app-store-connect-cli-skills/asc-ad-hoc-distribution)<a href="https://agentmods.dev/skills/rorkai/app-store-connect-cli-skills/asc-ad-hoc-distribution"><img src="https://agentmods.dev/badge/skills/rorkai/app-store-connect-cli-skills/asc-ad-hoc-distribution/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/rorkai/app-store-connect-cli-skills/asc-ad-hoc-distribution"><img src="https://agentmods.dev/badge/skills/rorkai/app-store-connect-cli-skills/asc-ad-hoc-distribution.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
- Socket pass
- Snyk pass
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Privilege Escalation · line 109 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
- medium Privilege Escalation · line 110 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
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.00062 | $0.01754 |
| Opus 5 | $0.00031 | $0.00877 |
| Sonnet 5 | $0.00012 | $0.00351 |
| Haiku 4.5 | $0.00006 | $0.00175 |
Grade B, and why
asc-ad-hoc-distribution scanned grade B with 1 finding 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 13d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
chmod 600 ".asc/distribution/config.json" ".asc/distribution/devices.json" Copies of this mod
1 near-identical copy found in the catalogue:
- asc-ad-hoc-distribution — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ASC ad hoc distribution
Use the experimental asc distribute workflow to turn an existing iOS archive
into a private, verified install link for registered devices. Use TestFlight or
the App Store release skills instead when the build should go through Apple-hosted
distribution.
Confirm the installed contract before acting:
asc distribute --help
asc distribute plan --help
asc distribute apply --help
asc distribute resume --help
asc distribute status --help
asc distribute verify --help
Choose the workflow
- Use
plan->apply->resume/status->verifyfor an end-to-end, hash-authorized run starting from an.xcarchive. - Use
inspect->prepare->publishonly when the caller already owns the ad hoc IPA and wants to operate the lower-level boundaries separately.
Guardrails
- Treat the distribution spec, devices file, PKCS#12 identity, password file, run state, and exact install-link artifact as private. Keep them out of Git and require owner-only permissions.
- Never put S3 credentials or presigned URLs in the distribution spec, command
output, logs, issues, or chat. Use
ASC_S3_ACCESS_KEY_ID,ASC_S3_SECRET_ACCESS_KEY, and optionalASC_S3_SESSION_TOKEN, or the standard AWS SDK credential chain. planis read-only and may exit successfully withready: false. Inspect the typed blockers and effects before continuing.applycan register missing devices, create safe App IDs and successor ad hoc profiles, write local artifacts, and publish immutable objects. Run it only after the user authorizes the exact plan hash and effect inventory.- The orchestrated workflow supports private access to an existing S3-compatible bucket. It does not create buckets, change policies, delete old builds, install the app, or launch it.
- Input drift, an immutable-object conflict, expired signing material, or an expired private link requires a new plan. Do not force the old run forward.
Preconditions
- An existing iOS
.xcarchivewith one main app target. Embedded apps, extensions, Watch apps, and App Clips make the v1 plan not ready. - A local iOS distribution PKCS#12 identity and optional protected password file.
- A protected strict-v1 devices file. For example:
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.
- 13d ago First seen · 190 lines · 62 tokens per session scan B a090ed8e82bc
asc-ad-hoc-distribution is a skill published in the GitHub repository rorkai/app-store-connect-cli-skills (1,025 stars, last pushed 4d ago), licensed MIT. It adds 62 tokens to every session and 1,754 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
app-rejection-recovery
Diagnoses App Store rejections, drafts Resolution Center responses, and plans the fix for resubmission. Use when the user says "my app was rejected", "Apple rejected my app", "App Review rejection", "guideline violation", "Resolution Center response", "guideline 2.1", "guideline 4.3", "guideline 5.1.1", "binary…
asc-submission
Prepare an app for App Store submission or TestFlight distribution using the App Store Connect MCP server. Use when user says "prepare submission", "submit to app store", "prepare for review", "update metadata", "set what's new", "check submission readiness", "distribute to testflight", or wants to manage App Store…
apple-app-delivery
Upload builds, distribute on TestFlight, manage metadata, submit for Beta/App Review, and release on the App Store using Apple's official CLIs and the App Store Connect API. Default stable delivery to APPSTORE so one build can be tested in TestFlight and later submitted to the App Store; choose TESTFLIGHTINTERNALONLY…
asc-build-check
Check the latest CI build status and debug failures using the App Store Connect MCP server. Use when user says "check build", "what broke", "CI status", "build failing", or asks about recent build failures. Also use for signing issues, provisioning profiles, bundle ID capabilities, or Developer Portal queries.
review-management
Pull, cluster, triage, and respond to App Store reviews via the App Store Connect MCP. Use when you need to fetch recent reviews, analyze sentiment, draft developer responses, track recurring themes as product signals, or close the loop on a rating recovery campaign. Trigger phrases: "triage reviews", "respond to…
asc-audit
Read-only drift check between live App Store Connect state, the repo, and whatever launch/submission docs claim. Use before quoting any build/version/TestFlight number back to the user, before trusting a canonical "where we stand" doc block, and as the required first step of submission-preflight before any submit.…