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 aroyburman-codes/pm-skills --skill launch-checklistgit clone --depth 1 https://github.com/aroyburman-codes/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/aroyburman-codes/pm-skills/launch-checklist)<a href="https://agentmods.dev/skills/aroyburman-codes/pm-skills/launch-checklist"><img src="https://agentmods.dev/badge/skills/aroyburman-codes/pm-skills/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/aroyburman-codes/pm-skills/launch-checklist"><img src="https://agentmods.dev/badge/skills/aroyburman-codes/pm-skills/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.00051 | $0.00943 |
| Opus 5 | $0.00026 | $0.00472 |
| Sonnet 5 | $0.00010 | $0.00189 |
| Haiku 4.5 | $0.00005 | $0.00094 |
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 9d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Launch Checklist Skill
Generate a comprehensive, customized launch readiness checklist for any product release.
When to Use
- User is preparing to launch a feature or product
- User needs to ensure nothing is missed before go-live
- User says
/launch-checklistfollowed by what they're launching - Any pre-launch review or go/no-go decision
Framework: Launch Readiness Checklist
Step 1: Scope the Launch
- What's launching? Feature name and brief description
- Launch type: Feature flag → Internal → Beta → GA
- Target date: When is this going live?
- Blast radius: How many users are affected?
- Reversibility: Can we roll back easily?
Step 2: Generate Checklist by Function
Engineering
- Code complete and merged to release branch
- Unit tests passing (coverage threshold met)
- Integration tests passing
- Load/performance testing complete (meets latency/throughput targets)
- Feature flag configured and tested (on/off/gradual rollout)
- Database migrations tested and reversible
- API versioning handled (no breaking changes for existing clients)
- Monitoring and alerting configured
- Logging sufficient for debugging
- Rollback procedure documented and tested
QA
- Test plan executed (happy path, edge cases, error states)
- Cross-browser/cross-platform testing complete
- Accessibility testing (screen reader, keyboard nav, contrast)
- Regression testing on adjacent features
- Security review complete (auth, input validation, data handling)
Design
- Final designs match implementation
- Empty states, loading states, error states all designed
- Mobile/responsive behavior verified
- Copy reviewed and finalized
- Animations/transitions smooth and performant
Legal & Compliance
- Privacy review complete (data collection, retention, deletion)
- Terms of service updated if needed
- GDPR/CCPA compliance verified
- Licensing for any third-party components cleared
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.
- 9d ago First seen · 113 lines · 51 tokens per session scan A f1a553274f6f
launch-checklist is a skill published in the GitHub repository aroyburman-codes/pm-skills (25 stars, last pushed 6mo ago), licensed MIT. It adds 51 tokens to every session and 943 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-08-30.
Other skills, from other repositories
release-skills
A release workflow for preparing and publishing a new version of a software project. A release is a named version that may include updated version files, release notes, tags, or a GitHub Release.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
version-release
Choose and apply the correct semantic version bump for this repository. Use for every user-visible release, before merge when a change set should ship as patch, minor, or major, and whenever package/plugin/desktop version metadata must stay synchronized.
changelog-gen
A changelog generator that turns Git history into a version-by-version record of project changes. A changelog is a readable summary of new features, fixes, breaking changes, documentation, and other updates.
pre-publish-review
Nuclear-grade 12-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (orchestrator manual QA plus one gate reviewer) for holistic review, and 1 oracle for overall release…
publish
Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts. Ship-only: never runs pre-publish-review or re-reviews merged code unless the user explicitly asks. Argument: . Triggers: publish, release, deploy, npm publish.