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 julianoczkowski/product-manager --skill pm-launch-plangit clone --depth 1 https://github.com/julianoczkowski/product-managerWrote 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/julianoczkowski/product-manager/pm-launch-plan)<a href="https://agentmods.dev/skills/julianoczkowski/product-manager/pm-launch-plan"><img src="https://agentmods.dev/badge/skills/julianoczkowski/product-manager/pm-launch-plan/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/julianoczkowski/product-manager/pm-launch-plan"><img src="https://agentmods.dev/badge/skills/julianoczkowski/product-manager/pm-launch-plan.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.00081 | $0.01272 |
| Opus 5 | $0.00041 | $0.00636 |
| Sonnet 5 | $0.00016 | $0.00254 |
| Haiku 4.5 | $0.00008 | $0.00127 |
Grade A, and why
pm-launch-plan 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 10d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Launch Plan (Pragmatic Framework: Programs → Launch, + Enablement)
Launch readiness is more than just product readiness. A launch is cross-functional: the product can be done while the market, the channel, and support are not. Plan, execute, and measure the launch as its own deliverable.
Reuse the positioning statement, personas, and launch trigger from earlier artifacts
in the feature dossier if they exist (positioning doc, personas, release charter —
see ../pm-copilot/references/artifact-output.md for how to find the dossier). See
../pm-copilot/references/framework.md for the Programs and Enablement boxes.
What a launch pulls together
- Programs: Awareness (raise profile in strategic segments), Nurturing (move prospects through the funnel), Advocacy (testimonials, case studies, references), Measurement.
- Enablement / Readiness: Sales Alignment (align selling to how the market buys), Content (per persona, per buying step), Sales Tools (per selling step), Channel Training (how to sell the product, not use it).
- Market Window: Marketing, Sales, and Operations work backward from the launch date while Development works to it. If the release is content-driven (no committed date — see the release charter), anchor the backward plan to the release's exit criteria instead, and re-forecast the launch date as they near completion.
Interview the user (batch questions)
- What's launching, at what scale/tier (major vs minor), and the target date/market window — or, for a content-driven release, the exit criteria that will trigger the launch?
- Launch goals & success metrics — awareness, pipeline, adoption, revenue?
- Target personas & positioning — who are we reaching, and what's the core message? (link the positioning doc)
- Channels & programs — how will we create awareness and nurture demand?
- Sales readiness — what content, tools, and training does the channel need?
- Cross-functional readiness — product, marketing, sales, support, ops, legal — who owns what, and what's the go/no-go bar?
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.
- 10d ago First seen · 107 lines · 81 tokens per session scan A e16e3f7e1cbe
pm-launch-plan is a skill published in the GitHub repository julianoczkowski/product-manager (31 stars, last pushed 1mo ago), licensed MIT. It adds 81 tokens to every session and 1,272 once invoked, about $0.0004 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
persona-import
This skill should be used when the user asks to "import a paperclip agent", "convert paperclip to woterclip", "migrate from paperclip", "import persona from paperclip", or wants to convert existing Paperclip agent directories into WoterClip persona format.
regulatory-review
This skill should be used when the user asks to "analyze regulations", "regulatory landscape", "compliance requirements", "legal considerations", "regulatory risk", "industry regulations", "compliance analysis", "regulatory trends", or needs guidance on understanding regulatory environments, compliance requirements…
persona-create
This skill should be used when the user asks to "create a persona", "add a new persona", "set up a new agent role", "add a woterclip persona", or runs the /persona-create command. Interactively creates a new WoterClip persona with SOUL.md, TOOLS.md, and config.yaml.
falsify
Adversarial falsification of sigint research findings. Generates disconfirming queries, executes web-only adversarial search, assigns ordinal verdicts (falsified | weakened | survived | inconclusive), and applies remediation (quarantine, confidence downgrade, follow-up queue). Invocable standalone via /sigint:falsify…
report-writing
This skill should be used when the user asks to "write a report", "executive summary", "research report format", "report structure", "present findings", "business writing", "analysis documentation", or needs guidance on structuring research outputs, executive communication, or professional report formatting.
tech-assessment
This skill should be used when the user asks to "assess technology", "technology evaluation", "tech stack analysis", "technical feasibility", "technology trends", "build vs buy", "technology roadmap", "architecture assessment", or needs guidance on evaluating technologies, technical due diligence, or technology…