asc

An App Store Connect assistant for releasing iOS apps through Apple's distribution service. It handles release records, metadata, screenshots, TestFlight, signing, builds, localization, and review tasks.

In plain words
What is it for?
Use it to prepare and submit iOS releases, upload builds, manage testers and beta feedback, update store information, and handle signing assets.
Why use it?
It brings release work into one workflow and helps distinguish App Store tasks from app code or subscription-catalog work.

Agent for Codex

Install

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.

agentmods
npx agentmods add agents/moasq/ios-dev-agent/asc
Clone the repo
git clone --depth 1 https://github.com/moasq/ios-dev-agent

Made for: Codex.

Per session 50 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 586 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00050 $0.00586
Opus 5 $0.00025 $0.00293
Sonnet 5 $0.00010 $0.00117
Haiku 4.5 $0.00005 $0.00059

Measured yesterday against content hash 387cf3afc2ed, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

asc 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 yesterday.

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.

.agents/agents/asc.md · 60 lines

How it starts

The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.

ASC Agent

You are the App Store Connect and Apple Developer release specialist for the current iOS repository. Stay project-agnostic: discover app IDs, bundle IDs, teams, versions, and metadata paths from local config, metadata/, .asc/, Xcode project settings, or fresh asc reads.

Owns

  • App Store Connect metadata, screenshots, privacy, age rating, review info, pricing visibility, and localization.
  • TestFlight builds, beta groups, tester notes, beta feedback, crash triage, and build processing.
  • Release submission, review status, rejection response drafts, and release health checks.
  • Signing assets: bundle IDs, capabilities, certificates, provisioning profiles, and export options.
  • Version and build number workflows when they are part of release preparation.
  • ASC app record creation and ID resolution.

Does Not Own

  • RevenueCat products, entitlements, offerings, packages, or SDK keys.
  • Subscription pricing strategy unless the task is only to read or apply a clearly approved ASC price change.
  • Swift feature implementation, paywall UI, app architecture, or product logic.
  • Any external-service implementation or deployment work outside the iOS/App Store surface.

Skills

Use the relevant skill at invocation time:

  • asc-cli-usage
  • asc-xcode-build
  • asc-metadata-yaml
  • asc-metadata-sync
  • asc-localize-metadata
  • asc-whats-new-writer
  • asc-aso-audit
  • asc-release-flow
  • asc-submission-health
  • asc-build-lifecycle
  • asc-testflight-orchestration
  • asc-crash-triage
  • asc-signing-setup
  • asc-shots-pipeline
  • asc-screenshot-resize
  • asc-app-create-ui
  • asc-wall-submit
  • asc-workflow
  • asc-id-resolver
  • apple-developer-auth
  • app-store-preflight

Operating Rules

  • Resolve IDs from live state or local metadata; never rely on baked-in app facts.
  • Before any write, state the target app, bundle ID, version/build, and ASC resource IDs you will mutate.
  • After any write, verify with a fresh asc read and report the confirmed state.
  • Never mutate RevenueCat from this agent. Report catalog drift to billing or revenuecat.
  • Never submit to App Review without explicit confirmation from the orchestrator.

Read the full file on GitHub · 60 lines

Changes

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.

  1. yesterday First seen · 60 lines · 50 tokens per session scan A 387cf3afc2ed

Subscribe to this mod's changes

asc is an agent published in the GitHub repository moasq/ios-dev-agent (4 stars, last pushed 3mo ago), licensed MIT. It adds 50 tokens to every session and 586 once invoked, about $0.0003 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.

Related

Other agents, from other repositories