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/raydeveloperf/app-store-connect-release-kit/asc-launch-workflownpx skills add raydeveloperF/App-Store-Connect-release-kit --skill asc-launch-workflowgit clone --depth 1 https://github.com/raydeveloperF/App-Store-Connect-release-kitWhat 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.00107 | $0.02913 |
| Opus 5 | $0.00053 | $0.01456 |
| Sonnet 5 | $0.00021 | $0.00583 |
| Haiku 4.5 | $0.00011 | $0.00291 |
Grade A, and why
asc-launch-workflow 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 2d 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 — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ASC Launch Workflow
Use this skill as the coordinator for a full ASC launch/update pass:
- localized metadata copy;
- localized keyword fields;
- localized ASC screenshot assets;
- ASC API task JSON and, after explicit confirmation, optional ASC execution.
Each phase runs in a dedicated subagent to keep the coordinator's context lean. The coordinator builds the shared product brief, dispatches subagents with precise inputs, collects their file outputs and summaries, assembles the review bundle, and handles the ASC mutation confirmation directly with the user. The coordinator never performs the work of a child skill inline.
If any child skill is missing or cannot be loaded, stop before the affected phase and report the missing dependency.
Security And Live-Update Rules
Never ask the user to paste App Store Connect secrets, .p8 contents, JWTs, Authorization headers, or ~/.asc_secrets.
Never read or print ~/.asc_secrets, .p8 private keys, tokens, Authorization headers, or full request headers.
Treat App Store Connect writes as a two-step process:
- Generate final ASC task JSON from reviewed artifacts.
- Stop and ask the user to confirm the exact JSON before any
POST,PATCH,DELETE, upload, submit, or state change.
Read-only ASC discovery may run when the task is clear and local access is available. Mutating ASC operations must never run in the same step that first creates the final JSON unless the user already explicitly approved that exact JSON.
Start Gate
Before starting any project inspection, subagent dispatch, hard dependency check, file generation, screenshot capture, App Store Connect discovery, or API task drafting, verify that the required inputs below are present.
Everything not listed here is either inferred from the project, defaulted automatically, or discovered at runtime. Do not ask the user for anything beyond this list.
Required inputs — the only things to block on:
| Input | Required when | Why it cannot be inferred |
|---|---|---|
| Phases to run | Always | User decision; cannot be guessed |
| Target locales | Always | User decision; cannot be guessed |
| Pixelmator Pro PXD template path | screenshots phase |
Stored in user's personal directory; not discoverable |
Intended ASC operation (draft-only / generate-task-json / execute-after-confirmation) |
asc-json or asc-execute phase |
Determines whether live App Store mutations happen; must be explicit |
What ships with it
1 file 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.
- 2d ago First seen · 325 lines · 107 tokens per session scan A e08419bf037e
asc-launch-workflow is a skill published in the GitHub repository raydeveloperF/App-Store-Connect-release-kit (2 stars, last pushed 2mo ago), licensed MIT. It adds 107 tokens to every session and 2,913 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
app-store-screenshots
End-to-end playbook for producing localized, caption-framed App Store screenshots (iPhone + iPad) from real simulator captures, then replacing them on App Store Connect. Use when asked to create, localize, redesign, or upload App Store screenshots for an iOS app. Covers capture automation via the accessibility tree…
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-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-iap-attach
Attach in-app purchases and subscriptions to an app version for App Store review. Use when the user has IAPs or subscriptions in "Ready to Submit" state that need to be included with a first-time version submission. Works for both first-time and subsequent submissions.
asc-privacy-nutrition-labels
Set up App Store privacy nutrition labels (data collection declarations) for an app. Use when the user needs to declare what data their app collects, how it's used, and whether it's linked to the user. Handles both "no data collected" and full data collection declarations.
asc-team-key-create
Create a new App Store Connect Team API Key with Admin permissions, download the one-time .p8 private key, and store it in /.blitz. Use when the user needs a new ASC API key for CLI auth, CI/CD, or external tooling.