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 exiao/pm-skills --skill launch-strategygit clone --depth 1 https://github.com/exiao/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/exiao/pm-skills/launch-strategy)<a href="https://agentmods.dev/skills/exiao/pm-skills/launch-strategy"><img src="https://agentmods.dev/badge/skills/exiao/pm-skills/launch-strategy/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/exiao/pm-skills/launch-strategy"><img src="https://agentmods.dev/badge/skills/exiao/pm-skills/launch-strategy.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.00058 | $0.01018 |
| Opus 5.5 | $0.00023 | $0.00407 |
| Sonnet 5.5 | $0.00012 | $0.00204 |
| Haiku 4.5 | $0.00006 | $0.00102 |
Grade A, and why
launch-strategy 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 2mo 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Launch Strategy
Expert in SaaS product launches and feature announcements. Plan launches that build momentum, capture attention, and convert interest into users.
Before Starting
Read .agents/product-marketing-context.md if it exists — it contains product name, audience, and positioning context.
Core Philosophy
The best companies don't launch once; they launch again and again. Every feature, improvement, and update is an opportunity to capture attention.
The ORB Framework
Structure launch marketing across three channel types. Everything funnels back to owned.
Owned Channels
You control the channel (email list, blog, podcast, community, website/product). Get more effective over time. No algorithm changes.
Start with 1-2 based on audience: blog if your industry lacks quality content, email if people want direct updates, community if engagement matters.
Rented Channels
Platforms providing visibility you don't control (social media, app stores, YouTube, Reddit). Pick 1-2 where your audience is active. Use them to drive traffic to owned channels.
Borrowed Channels
Tap someone else's audience (guest content, podcast interviews, collabs, speaking, influencer partnerships). Be proactive: list leaders your audience follows, pitch win-win collaborations.
Five-Phase Launch Approach
Phase 1: Internal Launch
Recruit early users to test for free. Collect feedback on usability gaps. Validate core functionality.
Phase 2: Alpha Launch
Create landing page with early access signup. Announce the product exists. Invite users individually.
Phase 3: Beta Launch
Work through early access list. Start marketing with teasers. Recruit friends, investors, influencers. Consider waitlist, "Beta" UI sticker, email invites.
Phase 4: Early Access Launch
Leak screenshots, GIFs, demos. Gather quantitative and qualitative data. Optionally run product/market fit survey. Expand via batch invites or open early access.
Phase 5: Full Launch
Open self-serve signups. Start charging. Announce across all channels.
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.
- 2mo ago First seen · 137 lines · 58 tokens per session scan A 833d85edcef7
launch-strategy is a skill published in the GitHub repository exiao/pm-skills (11 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 58 tokens to every session and 1,018 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-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…