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 agentmods add commands/phuryn/pm-skills/plan-launchgit clone --depth 1 https://github.com/phuryn/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/commands/phuryn/pm-skills/plan-launch)<a href="https://agentmods.dev/commands/phuryn/pm-skills/plan-launch"><img src="https://agentmods.dev/badge/commands/phuryn/pm-skills/plan-launch.svg" alt="Measured on agentmods" 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 | $0.00021 | $0.01061 |
| Opus 5 | $0.00010 | $0.00531 |
| Sonnet 5 | $0.00004 | $0.00212 |
| Haiku 4.5 | $0.00002 | $0.00106 |
Grade A, and why
plan-launch 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- plan-launch — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/plan-launch -- Go-to-Market Strategy
Build a complete GTM plan from first principles: identify your beachhead market, define the ideal customer, craft messaging, choose channels, and create a launch timeline.
Invocation
/plan-launch AI-powered proposal writer for consulting firms
/plan-launch New enterprise tier for our project management tool
/plan-launch [upload a PRD, strategy doc, or pitch deck]
Workflow
Step 1: Understand the Launch
Ask:
- What are you launching? (new product, new feature, new tier, market expansion)
- What stage? (pre-launch planning, imminent launch, post-launch optimization)
- Do you have existing customers? Or starting from zero?
- What's the timeline? Any hard deadlines?
- Budget constraints? Team size?
Step 2: Define Beachhead Segment
Apply the beachhead-segment skill:
- Evaluate potential market segments against:
- Burning pain (how urgently they need this)
- Willingness to pay (budget and purchase authority)
- Winnable market share (can you reach and win them)
- Referral potential (will they tell others)
- Recommend the single best starting segment with rationale
- Map adjacent segments for expansion after beachhead is secured
Step 3: Define Ideal Customer Profile
Apply the ideal-customer-profile skill:
- Demographics: company size, industry, geography, tech stack
- Behaviors: how they discover solutions, buying process, decision makers
- JTBD: specific jobs they're hiring your product for
- Current alternatives: what they use today and why it falls short
- Qualification criteria: how to identify them quickly
Step 4: Build GTM Strategy
Apply the gtm-strategy skill:
- Positioning: How you describe yourself to this segment
- Messaging: Key messages for different stakeholders (buyer, user, influencer)
- Channels: Where and how to reach your ICP (ranked by expected ROI)
- Launch tactics: Specific actions for pre-launch, launch day, and post-launch
- Pricing alignment: How pricing supports the GTM motion
- Success metrics: How you'll know the launch worked
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.
- 4d ago First seen · 131 lines · 21 tokens per session scan A 51efe35bf4db
plan-launch is a command published in the GitHub repository phuryn/pm-skills (25,964 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 1,061 once invoked, about $0.0001 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 commands, from other repositories
buyer-personas
Map the buying committee, then build alternatives-anchored messaging personas.
ideal-customer-profile
Build, enrich, or audit your ICP — trigger events, buyer map, JTBD, disqualifiers.
positioning-messaging
Build or audit positioning statements, messaging, and related output.
gtm-motions
Score and select a GTM motion stack against real deal economics, not a taxonomy tour.
interview-summary
Summarize a customer interview transcript using JTBD analysis.
prioritize
Score and rank initiatives using a GTM-native prioritization framework.