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 hamzafarooq/claude-code-starter --skill launch-checklistgit clone --depth 1 https://github.com/hamzafarooq/claude-code-starterWrote 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/hamzafarooq/claude-code-starter/launch-checklist)<a href="https://agentmods.dev/skills/hamzafarooq/claude-code-starter/launch-checklist"><img src="https://agentmods.dev/badge/skills/hamzafarooq/claude-code-starter/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/hamzafarooq/claude-code-starter/launch-checklist"><img src="https://agentmods.dev/badge/skills/hamzafarooq/claude-code-starter/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.00046 | $0.00434 |
| Opus 5.5 | $0.00018 | $0.00174 |
| Sonnet 5.5 | $0.00009 | $0.00087 |
| Haiku 4.5 | $0.00005 | $0.00043 |
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.
What it actually says
Ask the user:
- "What are you launching — a new feature, a product update, a new product, or something else?"
- "Who is the audience — existing users, new customers, enterprise, consumers?"
- "What's your target launch date and team size?"
Then produce a checklist organized by phase:
Launch Checklist: [Product/Feature Name]
Launch date: [X] Launch type: [soft launch / beta / public launch / coordinated release]
2 weeks before
- PRD finalized and reviewed by engineering lead
- Acceptance criteria written and QA plan in place
- Legal/compliance review completed (if applicable)
- Pricing and packaging confirmed
- Support documentation drafted
- Rollback plan documented
1 week before
- Feature flag / release toggle configured
- Analytics events implemented and verified in staging
- Email announcement drafted and approved
- In-app messaging or onboarding flow reviewed
- Customer success and support teams briefed
- Press / influencer outreach sent (if applicable)
Launch day
- Staged rollout configured (10% → 50% → 100%)
- Error monitoring and alerts confirmed active
- All-hands Slack channel open for real-time issues
- First metrics checkpoint scheduled (T+2h)
- Announcement posted (email / social / in-app)
Post-launch (first week)
- Day 1 and Day 7 metrics reviewed against target
- User feedback collected (in-app, support tickets, interviews)
- Known issues triaged and prioritized
- Internal retro scheduled
Mark any item that is blocked or unassigned — those are your launch risks.
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 · 52 lines · 46 tokens per session scan A 6084c37b60b6
launch-checklist is a skill published in the GitHub repository hamzafarooq/claude-code-starter (145 stars, last pushed 7d ago), licensed MIT. It adds 46 tokens to every session and 434 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
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
remove
Remove a deployed framework or addon from the current workspace.