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 OneWave-AI/claude-skills --skill product-launch-war-roomgit clone --depth 1 https://github.com/OneWave-AI/claude-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/onewave-ai/claude-skills/product-launch-war-room)<a href="https://agentmods.dev/skills/onewave-ai/claude-skills/product-launch-war-room"><img src="https://agentmods.dev/badge/skills/onewave-ai/claude-skills/product-launch-war-room/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/onewave-ai/claude-skills/product-launch-war-room"><img src="https://agentmods.dev/badge/skills/onewave-ai/claude-skills/product-launch-war-room.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00078 | $0.01060 |
| Opus 5 | $0.00039 | $0.00530 |
| Sonnet 5 | $0.00016 | $0.00212 |
| Haiku 4.5 | $0.00008 | $0.00106 |
Grade A, and why
product-launch-war-room 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Launch War Room
A launch fails for boring reasons: nobody owned the objection, the price change leaked, the segment that mattered wasn't in the room. This skill runs the war room that catches those reasons before launch day — adversarial by design, decision-oriented, and grounded in your real customers when data is available.
It composes the panel skills (customer-panel-of-experts, prospect-panel-simulator) into a single GTM decision and a rollout plan you can execute.
What it's for
- New product / feature launch
- Repositioning or rebrand
- Price increase or packaging change (hand the rollout to
pricing-change-strategist) - Market or segment expansion
- Sunsetting something customers depend on
Step 1 — Define the launch
Lock these before any debate:
- What's launching and what specifically changes for the customer.
- Audience — existing customers, prospects, a specific segment, the market.
- Goal + metric — the number that defines success and the window to hit it.
- Constraints — timeline, budget, team, dependencies, hard commitments already made.
- Reversibility — fully reversible / costly / one-way door. This sets how much rigor the war room applies.
Step 2 — Convene the room
Seat both sides. Use icp-deep-scanner personas where the call is customer-facing; add functional experts for execution risk:
- Customer voice — relevant buyer personas (load from
personas/; if absent and tools are connected, runicp-deep-scannerread-only; otherwise mark PROVISIONAL). - The skeptic / pre-mortem lead — assumes the launch already failed and explains why.
- Functional experts as the launch demands — GTM/demand-gen, sales, product, support/CS, finance, brand. Each owns the risks in their lane.
For a thorough war room, dispatch parallel sub-agents (one per role) via /agent-army, then synthesize. Connections are read-only; no external sends; no real PII; secrets in env vars only.
Step 3 — Pre-mortem and debate
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 · 82 lines · 78 tokens per session scan A 885ac3cf8448
product-launch-war-room is a skill published in the GitHub repository OneWave-AI/claude-skills (291 stars, last pushed 1mo ago), licensed MIT. It adds 78 tokens to every session and 1,060 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-09-03.
Other skills, from other repositories
analytics-strategy
Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy. Use this skill whenever the user wants to plan analytics, design dashboards, build event taxonomies, define KPIs, set up tracking, or audit existing measurement.…
content-strategy
Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning. Use this skill whenever the user wants to plan a content program, define content pillars, build an editorial calendar, structure topic clusters, set up content governance, or align…
incident-response
Manage active production incidents through detection, triage, mitigation, communication, and resolution with structured roles and decision-making. Use this skill whenever the user has an active incident, a production issue, a service outage, a security incident, or needs to plan incident response procedures. Triggers…
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.
agb-begriff-vorformuliert-305
Für AGB Begriff Vorformuliert 305: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: agb-begriff-vorformuliert-305.