agentmods.dev

asc-build-lifecycle

asc-build-lifecycle is a skill for Claude Code from hanamizuki/solopreneur. It costs 31 tokens per session (426 once invoked), scanned A, a copy of asc-build-lifecycle, MIT.

A workflow for managing an app's uploaded builds in App Store Connect, Apple's service for testing and distributing Apple apps. It covers build processing, finding builds, choosing the next build number, publishing, and removing old builds.

In plain words
What is it for?
It helps inspect build status, find recent or latest builds, calculate the next usable build number, publish to TestFlight or the App Store, and preview or apply expiration of old builds.
Why use it?
Builds can be delayed during processing, have confusing numbers, or accumulate until storage and account management become difficult. This workflow provides checks and cleanup steps.

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

not rated 154repo +2 4d ago A scan 31 tokens copy · 89% MIT

Good fit It helps inspect build status, find recent or latest builds, calculate the next usable build number, publish to TestFlight or the App Store, and preview or apply expiration of old builds.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hanamizuki/solopreneur/asc-build-lifecycle
View source ↗ hanamizuki/solopreneur
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-build-lifecycle
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-build-lifecycle

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/hanamizuki/solopreneur/asc-build-lifecycle"><img src="https://agentmods.dev/badge/skills/hanamizuki/solopreneur/asc-build-lifecycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 426 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 89% 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.00031 $0.00426
Opus 5.5 $0.00012 $0.00170
Sonnet 5.5 $0.00006 $0.00085
Haiku 4.5 $0.00003 $0.00043

Measured 20d ago against content hash 3701648fb9f7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

asc-build-lifecycle 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

89% identical to asc-build-lifecycle — 3 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-build-lifecycle/SKILL.md · 38 lines

What it actually says

asc build lifecycle

Use this skill to manage build state, processing, and retention.

Find the right build

  • Latest build:
    • asc builds info --app "APP_ID" --latest --version "1.2.3" --platform IOS
  • Next safe build number:
    • asc builds next-build-number --app "APP_ID" --version "1.2.3" --platform IOS
    • The command scans the full processed-build history and in-flight uploads, then returns one greater than the highest positive numeric build number. Blank or non-numeric processed build numbers are skipped with a warning; if no usable number remains, it falls back to --initial-build-number.
  • Recent builds:
    • asc builds list --app "APP_ID" --sort -uploadedDate --limit 10

Inspect processing state

  • asc builds info --build-id "BUILD_ID"

Distribution flows

  • Prefer end-to-end:
    • asc publish testflight --app "APP_ID" --ipa "./app.ipa" --group "GROUP_ID" --wait
    • asc publish appstore --app "APP_ID" --ipa "./app.ipa" --version "1.2.3" --wait --submit --confirm

Cleanup

  • Preview expiration:
    • asc builds expire-all --app "APP_ID" --older-than 90d --dry-run
  • Apply expiration:
    • asc builds expire-all --app "APP_ID" --older-than 90d --confirm
  • Single build:
    • asc builds expire --build-id "BUILD_ID" --confirm

Notes

  • asc builds upload prepares upload operations only; use asc publish for end-to-end flows.
  • For long processing times, use --wait, --poll-interval, and --timeout where supported.
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 · 38 lines · 31 tokens per session scan A 3701648fb9f7

Subscribe to this mod's changes

asc-build-lifecycle is a skill published in the GitHub repository hanamizuki/solopreneur (154 stars, last pushed 4d ago), licensed MIT. It adds 31 tokens to every session and 426 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to asc-build-lifecycle, differing in 3 lines, and is treated as a copy.

DevOps and cloud
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