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 skills add hanamizuki/solopreneur --skill asc-release-flowgit clone --depth 1 https://github.com/hanamizuki/solopreneurWrote 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.
[](https://agentmods.dev/skills/hanamizuki/solopreneur/asc-release-flow)<a href="https://agentmods.dev/skills/hanamizuki/solopreneur/asc-release-flow"><img src="https://agentmods.dev/badge/skills/hanamizuki/solopreneur/asc-release-flow/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.
<a href="https://agentmods.dev/skills/hanamizuki/solopreneur/asc-release-flow"><img src="https://agentmods.dev/badge/skills/hanamizuki/solopreneur/asc-release-flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00071 | $0.01639 |
| Opus 5.5 | $0.00028 | $0.00656 |
| Sonnet 5.5 | $0.00014 | $0.00328 |
| Haiku 4.5 | $0.00007 | $0.00164 |
Grade A, and why
asc-release-flow 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.
This is a copy
100% identical to asc-release-flow — 24 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.
How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
App Store release orchestration
Use this skill to carry a release from an approved plan to App Store review. Keep Game Center item preparation here; keep other blocker diagnosis and review recovery in asc-submission-health.
Ownership boundary
This skill owns:
- staging metadata and attaching a build;
- publishing an IPA or building locally;
- submitting a prepared version;
- assembling a multi-item review submission.
Use the preparation section for Game Center item preparation or attachment blockers. Use that reference's assembly and submission sections only after the app version is staged and the multi-item lane is selected. Stop and use asc-submission-health for other validation blockers, a stuck submission, cancellation, or retry decisions.
Preconditions
- Resolve
APP_ID, the version string,VERSION_IDwhen needed, andBUILD_IDwhen a build already exists. - Configure auth with
asc auth loginorASC_*environment variables. - Confirm the intended platform. Use
IOSunless the app targets another platform. - Keep canonical metadata in
./metadatawhen the workflow applies metadata. - Require a dry run before a mutating high-level command, then require
--confirmfor submission.
Choose the release lane
| Intent | Command |
|---|---|
| Prepare metadata and attach an existing build without submitting | asc release stage |
| Submit an already prepared version | asc review submit |
| Upload an IPA or build locally, then optionally submit | asc publish appstore |
| Submit the app version with IAP, subscription, or Game Center version items | lower-level asc review submission commands |
Do not mix lanes after one has already created a review submission. Inspect the existing submission first and continue through the matching lower-level commands.
Run the readiness gate
Apply this gate to a version that already has the intended build attached. For the staging lane, first complete Stage an existing build; asc release stage attaches the build and runs validation, after which this gate can be evaluated. Do not route an expected pre-staging "build not attached" result to asc-submission-health.
What ships with it
2 files 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.
- 20d ago First seen · 162 lines · 71 tokens per session scan A 744944011b75
asc-release-flow is a skill published in the GitHub repository hanamizuki/solopreneur (154 stars, last pushed 4d ago), licensed MIT. It adds 71 tokens to every session and 1,639 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to asc-release-flow, differing in 24 lines, and is treated as a copy.
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
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…
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…