asc-cli-usage

A reference for using the asc command-line tool to work with App Store Connect, Apple's service for managing app releases and distribution. It explains commands, options, login, JSON output, pagination, and safe update patterns.

In plain words
What is it for?
Use it to discover and run asc commands for app records, builds, versions, pricing, availability, and other App Store Connect data.
Why use it?
It reduces errors when automating or debugging App Store Connect tasks from a terminal or script.

Skill for Claude CodeCodex

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 skills/moasq/ios-dev-agent/asc-cli-usage
Any agent
npx skills add moasq/ios-dev-agent --skill asc-cli-usage
Clone the repo
git clone --depth 1 https://github.com/moasq/ios-dev-agent

Made for: Claude Code, Codex.

Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 578 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.00043 $0.00578
Opus 5 $0.00022 $0.00289
Sonnet 5 $0.00009 $0.00116
Haiku 4.5 $0.00004 $0.00058

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

Security

Grade A, and why

asc-cli-usage 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/skills/asc-cli-usage/SKILL.md · 49 lines

How it starts

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

asc cli usage

Use this skill when you need to run or design asc commands for App Store Connect.

Command discovery

  • Always use --help to discover commands and flags.
    • asc --help
    • asc builds --help
    • asc builds list --help

Canonical verbs (current asc)

  • Prefer view over legacy get aliases for read-only commands in docs and automation.
    • asc apps view --id "APP_ID"
    • asc versions view --version-id "VERSION_ID"
    • asc pricing availability view --app "APP_ID"
  • Prefer edit for update-only availability surfaces and other canonical edit flows.
    • asc pricing availability edit --app "APP_ID" --territory "USA,GBR" --available true
    • asc app-setup availability edit --app "APP_ID" --territory "USA,GBR" --available true
    • asc xcode version edit --build-number "42"
  • Keep set where the CLI intentionally models a higher-level replacement/configuration flow and --help still shows set as the canonical verb.

Flag conventions

  • Use explicit long flags (e.g., --app, --output).
  • Prefer explicit flags in automation; some newer commands can prompt for missing fields when run interactively.
  • Destructive operations require --confirm.
  • Use --paginate when the user wants all pages.

Output formats

  • Output defaults are TTY-aware: table in interactive terminals, json when piped or non-interactive.
  • Use --output table or --output markdown only for human-readable output.
  • --pretty is only valid with JSON output.

Authentication and defaults

  • Prefer keychain auth via asc auth login.
  • Fallback env vars: ASC_KEY_ID, ASC_ISSUER_ID, ASC_PRIVATE_KEY_PATH, ASC_PRIVATE_KEY, ASC_PRIVATE_KEY_B64.
  • ASC_APP_ID can provide a default app ID.
  • When permissions are unclear, inspect exact API key role coverage with asc web auth capabilities.
    • This lives under the experimental web auth surface.
    • It can resolve the current local auth by default, or inspect a specific key with --key-id.

Timeouts

  • ASC_TIMEOUT / ASC_TIMEOUT_SECONDS control request timeouts.
  • ASC_UPLOAD_TIMEOUT / ASC_UPLOAD_TIMEOUT_SECONDS control upload timeouts.

Read the full file on GitHub · 49 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 · 49 lines · 43 tokens per session scan A ae9c38c2c691

Subscribe to this mod's changes

asc-cli-usage is a skill published in the GitHub repository moasq/ios-dev-agent (4 stars, last pushed 3mo ago), licensed MIT. It adds 43 tokens to every session and 578 once invoked, about $0.0002 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 skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens