asc-cli-usage

asc-cli-usage is a skill for Claude Code from hanamizuki/solopreneur. It costs 46 tokens per session (1,261 once invoked), scanned A, a copy of asc-cli-usage, MIT.

A reference for using the asc command-line tool to work with App Store Connect. It explains how to discover commands, inspect API schemas, choose output formats, handle pagination, and check authentication and workflow coverage.

In plain words
What is it for?
It helps design or run commands for apps, builds, pricing, releases, and other App Store Connect tasks.
Why use it?
Command-line tools change over time and may support only part of an App Store Connect workflow. This reference reduces guesswork about commands, flags, results, and API limits.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the ios-dev plugin — 26 skills, 1 agent shipped together

Good fit It helps design or run commands for apps, builds, pricing, releases, and other App Store Connect tasks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hanamizuki/solopreneur/asc-cli-usage
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.

Any agent
npx skills add hanamizuki/solopreneur --skill asc-cli-usage
Clone the repo
git clone --depth 1 https://github.com/hanamizuki/solopreneur

Made for: Claude Code.

Or install ios-dev, the plugin that ships this one along with the rest of its 26 skills, 1 agent.

Wrote 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.

agentmods badge for asc-cli-usage

README.md
[![agentmods](https://agentmods.dev/badge/skills/hanamizuki/solopreneur/asc-cli-usage/github.svg)](https://agentmods.dev/skills/hanamizuki/solopreneur/asc-cli-usage)
Your own site
<a href="https://agentmods.dev/skills/hanamizuki/solopreneur/asc-cli-usage"><img src="https://agentmods.dev/badge/skills/hanamizuki/solopreneur/asc-cli-usage/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.

agentmods 80×15 button for asc-cli-usage

Your own site · 80×15
<a href="https://agentmods.dev/skills/hanamizuki/solopreneur/asc-cli-usage"><img src="https://agentmods.dev/badge/skills/hanamizuki/solopreneur/asc-cli-usage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,261 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.1 $0.00046 $0.01261
Opus 5.5 $0.00018 $0.00504
Sonnet 5.5 $0.00009 $0.00252
Haiku 4.5 $0.00005 $0.00126

Measured 20d ago against content hash d6184b413f6a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 20d 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.

Origin

This is a copy

100% identical to asc-cli-usage — 15 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/claude/ios-dev/skills/asc-cli-usage/SKILL.md · 76 lines

How it starts

The opening of the file, as written. The whole thing — 76 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
  • Use asc search for local, deterministic command discovery when you know the workflow but not the command path.
    • asc search "submit app for review"
    • asc search --output table "upload build"
  • Use asc schema to inspect bundled App Store Connect endpoint schemas and request/query fields before designing API-facing commands.
    • asc schema --pretty "GET /v1/apps"
    • asc schema --method POST appStoreVersions
  • Use asc capabilities to explain CLI-supported, partial, web-session, and public-API-limited workflow coverage.
    • asc capabilities --area release --output table
    • asc capabilities --status web-session --output table
    • asc capabilities --status not-public-api --output markdown

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"
  • Use asc pricing availability create to initialize app availability before using the update-only edit command. If Apple rejects the public-API bootstrap, authenticate a web session and use asc web apps availability create, or configure Pricing and Availability in App Store Connect.
    • asc pricing availability create --app "APP_ID" --territory "USA,GBR" --available true --available-in-new-territories true
    • asc web apps availability create --app "APP_ID" --territory "USA,GBR" --available-in-new-territories true
  • Keep set where the CLI intentionally models a higher-level replacement/configuration flow and --help still shows set as the canonical verb.

Read the full file on GitHub · 76 lines

Files

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.

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. 20d ago First seen · 76 lines · 46 tokens per session scan A d6184b413f6a

Subscribe to this mod's changes

asc-cli-usage is a skill published in the GitHub repository hanamizuki/solopreneur (154 stars, last pushed 4d ago), licensed MIT. It adds 46 tokens to every session and 1,261 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to asc-cli-usage, differing in 15 lines, and is treated as a copy.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

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

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 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

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens