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 hardiktiwari/PM-operating-OS --skill launch-readinessgit clone --depth 1 https://github.com/hardiktiwari/PM-operating-OSWrote 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/hardiktiwari/pm-operating-os/launch-readiness)<a href="https://agentmods.dev/skills/hardiktiwari/pm-operating-os/launch-readiness"><img src="https://agentmods.dev/badge/skills/hardiktiwari/pm-operating-os/launch-readiness/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/hardiktiwari/pm-operating-os/launch-readiness"><img src="https://agentmods.dev/badge/skills/hardiktiwari/pm-operating-os/launch-readiness.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.00032 | $0.00526 |
| Opus 5 | $0.00016 | $0.00263 |
| Sonnet 5 | $0.00006 | $0.00105 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
launch-readiness 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Launch Readiness
Help PMs run launch readiness checklists and make go/no-go recommendations. Ensures launches are planned, risks are surfaced, and stakeholders are aligned.
When to Use
- Before a feature launch
- Before an experiment rollout
- Before a product release
- Go/no-go meeting prep
- When asked "are we ready to launch?"
Process / Template
1. Define Launch Scope
- What is being launched? (feature, experiment, release)
- Target audience and rollout plan (% of users, segments)
- Launch date and any phased milestones
2. Run the Checklist
Product & Quality
- All P0/P1 bugs resolved or accepted
- Acceptance criteria met
- Edge cases and error states handled
- Rollback plan documented
Technical
- Feature flags / kill switches in place
- Monitoring and alerting configured
- Performance and load tested (if applicable)
- Data pipeline or analytics verified
Legal, Compliance, Security
- Legal review complete (if required)
- Privacy/compliance checks done
- Security review (if applicable)
Go-to-Market
- Support team briefed and docs updated
- Customer-facing comms ready (if applicable)
- Internal launch post drafted
Stakeholders
- Key stakeholders informed
- Escalation path defined
- Post-launch review scheduled
3. Assess Risks
- What could go wrong?
- Mitigation in place?
- Acceptable residual risk?
4. Make Go/No-Go Recommendation
| Status | Criteria |
|---|---|
| Go | All critical items green, risks acceptable |
| Conditional Go | Minor items open; launch with monitoring |
| No-Go | Critical gaps; delay until resolved |
5. Document Decision
- Summary of checklist outcome
- Open items and owners
- Go/no-go recommendation with rationale
- Next steps (if no-go or conditional)
Output
A Launch Readiness Summary including:
- Checklist status (green/yellow/red per area)
- Risk assessment
- Go/no-go recommendation
- Open items with owners
- Post-launch plan (monitoring, review)
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 · 84 lines · 32 tokens per session scan A 3f72438436b3
launch-readiness is a skill published in the GitHub repository hardiktiwari/PM-operating-OS (5 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 526 once invoked, about $0.0002 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-31.
Other skills, from other repositories
bcc-throughline
BCC global progress cockpit (plans.md/progress.md/findings.md). Slash: /bcc-throughline · chat: bcc:throughline · "where are we" · reprioritize · resume after /clear. Not for coding or full PLAN grill.
handoff
Guides the Claude Code agent through completing a task, selecting a handoff tier, building a valid completion-card, and performing a clean task handoff.
execute-plan
Implement a written plan (from write-plan or interview-plan) when the user says execute or implement it. Loads the plan, executes ready tasks in waves in the ticket venue, runs the plan's review gate itself. Do not use while still interviewing or writing the plan.
generate-stories
Translate a single Epic into clear, actionable User Stories with explicit acceptance criteria. Activate when an Epic is defined and work needs to be prepared for Delivery execution.
review-input
Adversarial review of any input (human idea, agent analysis, research report, feedback, observation) BEFORE it mutates persistent project state. Universal interceptor with domain auto-detection, 2-phase classification + evaluation, and triple-verdict output (veracity / fit / actionability). Anti-girouette guardrail…
review-story-alignment
Adversarial review of generated stories against the Discovery Session Brief, referenced DECs, and Epic DoR. Detects contradictions, omissions, and intent drift BEFORE stories reach Delivery. Produces a structured verdict (PASS/FAIL) with specific findings per story. Triggers after generate-stories, before backlog…