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 cnfeat/top-pm-skills --skill product-launch-checklistgit clone --depth 1 https://github.com/cnfeat/top-pm-skillsWrote 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/cnfeat/top-pm-skills/product-launch-checklist)<a href="https://agentmods.dev/skills/cnfeat/top-pm-skills/product-launch-checklist"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/product-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/cnfeat/top-pm-skills/product-launch-checklist"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/product-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.00064 | $0.01407 |
| Opus 5 | $0.00032 | $0.00704 |
| Sonnet 5 | $0.00013 | $0.00281 |
| Haiku 4.5 | $0.00006 | $0.00141 |
Grade A, and why
product-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 7d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Launch Checklist Skill
Never launch without checking everything. Generate a complete, role-assigned checklist covering pre-launch readiness, launch day execution, and post-launch monitoring.
Required Inputs
Ask the user for these if not provided:
- Launch name and planned launch date
- Launch tier (1 = major product launch, 2 = significant feature release, 3 = incremental update)
- Team members and their roles (engineering lead, PM, marketing, support, etc.)
- Feature description (what is being launched)
- Rollback capability (can this be feature-flagged or reverted quickly?)
How to Use This Skill
Provide:
- Launch name and date
- Launch tier (1 = major, 2 = feature, 3 = incremental)
- Team members and their roles
The skill generates a tiered checklist. Tier 3 launches use only the Essentials section. Tier 2 adds Marketing & Comms. Tier 1 uses all sections.
Output Format
Launch Checklist — [Feature/Product Name] — Target Date: [Date]
Launch Tier: [1 / 2 / 3] Launch Owner: [PM Name] Engineering Lead: [Name] Go/No-Go Decision By: [Date and time — typically 24 hours before launch]
🔧 PRE-LAUNCH — Engineering & Product (T-2 weeks)
- Feature flag created and tested in staging
- All acceptance criteria signed off by PM
- Code reviewed and merged to main
- QA sign-off completed (regression + new feature)
- Performance testing completed (load, latency)
- Security review completed (if data or auth changes)
- Rollback procedure documented and tested
- Monitoring and alerting configured
- Error logging in place with correct severity levels
- Database migrations tested on staging with production data volume
📢 PRE-LAUNCH — Marketing & Comms (T-1 week)
- Blog post written, reviewed, and scheduled
- In-app announcement or tooltip configured
- Email campaign drafted and QA'd
- Social media posts drafted and scheduled
- Landing page or feature page live in staging
- Press outreach sent (Tier 1 only)
- Product Hunt / community posts prepared (Tier 1 only)
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.
- 7d ago First seen · 143 lines · 64 tokens per session scan A 0d53bc456479
product-launch-checklist is a skill published in the GitHub repository cnfeat/top-pm-skills (48 stars, last pushed 3mo ago), licensed MIT. It adds 64 tokens to every session and 1,407 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.