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 cenconq25/claude-code-app-studio --skill release-checklistgit clone --depth 1 https://github.com/cenconq25/claude-code-app-studioWrote 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/cenconq25/claude-code-app-studio/release-checklist)<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/release-checklist"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/release-checklist/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/cenconq25/claude-code-app-studio/release-checklist"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/release-checklist.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.00051 | $0.01855 |
| Opus 5 | $0.00026 | $0.00928 |
| Sonnet 5 | $0.00010 | $0.00371 |
| Haiku 4.5 | $0.00005 | $0.00186 |
Grade A, and why
release-checklist 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Checklist
The build-and-submit gate. Confirms the candidate build is signed,
versioned, certified, and ready for store review. This is the technical
twin of /launch-checklist.
Phase 1: Read Project Context
Read in parallel:
CLAUDE.md— project name, version baseline..claude/docs/technical-preferences.md— framework, target platforms.- Current milestone in
production/milestones/. - Any prior release log in
production/releases/.
Capture target version from the user. Default convention: MAJOR.MINOR.PATCH
plus a build number that increments per submission.
Phase 2: Code Health Sweep
Run quick scans via Bash:
- TODO / FIXME / HACK counts:
rg -c '\b(TODO|FIXME|HACK)\b' --no-heading | sort - Skipped tests: grep for
xtest,xit,test.skip,it.skip,@Disabled,@Ignore. - Unused dependencies (best-effort per stack):
npx depcheckfor RN/JS.flutter pub depsreview for Flutter. - Bundle / size deltas vs the previous release.
Report counts and list anything that increased significantly.
Phase 3: Build the Checklist
# Release Checklist — [version] — [platform]
Generated: [date]
## Codebase Health
- TODO count: [N]
- FIXME count: [N] — review each before release
- HACK count: [N]
- Skipped tests: [N] — confirm each has a tracking note
## Build Verification
- [ ] Clean build succeeds on every target platform.
- [ ] Zero warnings (or each warning is annotated as accepted).
- [ ] Build size within budget.
- [ ] Bundle / IPA / AAB produced from a tagged commit.
- [ ] Build is reproducible — same SHA -> same artifact hash.
- [ ] Source maps / dSYMs / mapping files archived.
- [ ] Build configured for production — no `debug`, `staging`, `mock`
flags shipped.
## Versioning
- [ ] Version string matches the declared release.
- [ ] iOS `CFBundleShortVersionString` and `CFBundleVersion` set.
- [ ] Android `versionName` and `versionCode` set.
- [ ] React Native bundle and any OTA channel correctly named.
- [ ] Tag pushed to remote.
## Quality Gates
- [ ] QA sign-off APPROVED (or APPROVED WITH CONDITIONS resolved).
- [ ] Smoke check PASS on Tier A devices.
- [ ] Soak test PASS (if release-tier).
- [ ] No S1 / S2 bugs open.
- [ ] Performance budgets PASS.
- [ ] No memory leaks over the soak window.
- [ ] No crashes recorded during smoke + soak runs.
- [ ] Regression suite green.
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.
- 5d ago First seen · 256 lines · 51 tokens per session scan A e70322233c73
release-checklist is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 51 tokens to every session and 1,855 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-09-03.
Other skills, from other repositories
orca-emulator-android
Android device and emulator control from inside Orca over adb, with the live device view in Orca's emulator pane. Use when driving an adb-connected emulator or phone on Windows, Linux, or macOS: booting AVDs, taps, swipes, typing, hardware buttons, rotation, app install and launch, runtime permissions, the…
android-tombstone-symbolication
Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app…
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
winapp-maui
Package and sign .NET MAUI Windows apps with winapp, resolving the resizetizer manifest dependency. Use when packaging or signing a .NET MAUI Windows app, building a MAUI MSIX or signed unpackaged build in CI, or fixing 'manifest contains unresolved placeholders ($placeholder$)' errors from winapp package.
apple-search-ads
When the user wants to set up, optimize, or scale Apple Search Ads (ASA) campaigns — including keyword bidding, match types, campaign structure, Creative Product Sets, CPP routing, and ROAS optimization. Use when the user mentions "Apple Search Ads", "ASA", "Search Ads", "Search tab ads", "Today tab ads", "CPT"…
android-pentest
A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.