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 launch-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/launch-checklist)<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/launch-checklist"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/launch-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/launch-checklist"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/launch-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.00044 | $0.02068 |
| Opus 5.5 | $0.00018 | $0.00827 |
| Sonnet 5.5 | $0.00009 | $0.00414 |
| Haiku 4.5 | $0.00004 | $0.00207 |
Grade A, and why
launch-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 1mo 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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Launch Checklist
The cross-functional readiness gate. /release-checklist covers code
and store metadata; this skill goes wider — marketing, legal, privacy,
support, community, infrastructure — so nothing important slips.
Phase 1: Resolve Platform Scope
Default to both. If the project targets only iOS or only Android,
consult .claude/docs/technical-preferences.md for Target Platforms.
Ask the user the launch date and any soft-launch geography.
Phase 2: Read Project Context
Read in parallel:
CLAUDE.md,.claude/docs/technical-preferences.md.- Current milestone in
production/milestones/. - Latest QA sign-off from
production/qa/qa-signoff-*.md. - Latest perf profile from
production/perf/perf-profile-*.md. - Latest security audit from
production/security/security-audit-*.md. - Latest asset audit from
production/assets/asset-audit-*.md. - Latest balance check from
production/balance/balance-check-*.md. - Latest localization report from
production/localization/loc-report-*.md. - Tech debt register from
docs/tech-debt.md.
Surface the freshness of each artifact ("QA sign-off is 11 days old — re-run?").
Phase 3: Build the Master Checklist
Render a structured checklist. Each line is a checkbox the user can work through. The skill is a generator; signing off is the user's job.
Code and Build
- Latest QA sign-off is APPROVED (or APPROVED WITH CONDITIONS that have been resolved).
- Smoke check PASS on each Tier A device.
- Soak test PASS for the chosen scenario set.
- Performance budgets all PASS (cold start, frame, memory, battery, app size).
- Security audit RELEASE OK or RELEASE WITH PLAN (every P0 has a tracked fix).
- Regression suite green.
- No open S1 / S2 bugs.
- Tech debt register reviewed; no externally-deadlined item is unscheduled.
- Release branch tagged and signed.
- Crash reporting (Crashlytics / Sentry) live and verified receiving from the candidate build.
- Analytics live and verified (events fire on candidate build).
- Remote config / feature flags reviewed for safe defaults.
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.
- 1mo ago First seen · 275 lines · 44 tokens per session scan A 2986556e4fde
launch-checklist is a skill published in the GitHub repository cenconq25/claude-code-app-studio (42 stars, last pushed 5mo ago), licensed MIT. It adds 44 tokens to every session and 2,068 once invoked, about $0.0002 per session on Opus 5.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
vendor-review
Evaluate a vendor — cost analysis, risk assessment, and recommendation. Use when reviewing a new vendor proposal, deciding whether to renew or replace a contract, comparing two vendors side-by-side, or building a TCO breakdown and negotiation points before procurement sign-off.
integration-management
Post-closing M&A integration tracker — phased workplan, consent tracking, contract assignment at scale, weekly status reports. Initializes from whatever deal artifacts are available (purchase agreement, deal summary, closing checklist) and connects to deal-context.md and closing-checklist.yaml from the M&A cold-start.…
entity-compliance
Entity compliance tracker — initialize, report upcoming deadlines, update status, run health audit, export to CSV. Maintains a compliance-tracker.yaml built from the entity table, calculates filing deadlines by entity and jurisdiction, and surfaces what's due in the next 30/60/90 days. Use when user says "entity…
portfolio
Track the IP portfolio — registrations, renewals, maintenance fees, and use declarations. Use when checking what's renewing, adding or updating an asset, recording a maintenance filing, or auditing the register for gaps, lapses, and use-in-commerce questions. Receives handoffs from prosecution and clearance work.
launch-review
Full launch review against your framework and risk calibration. Use when the user says "review this launch", "legal review for [feature]", "can we ship this", "what are the legal issues with [product]", or references a launch tracker ticket or PRD that needs a category-by-category review memo.
gap-surfacer
Reference: shared gap- and comment-tracker framework backing /regulatory-legal:gaps and /regulatory-legal:comments. Tracks open policy gaps with remediation status, ingests gaps from policy-diff, surfaces what's open and aging, routes to owners, and notifies gap owners via Slack with per-send confirmation. Loaded by…