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 tjboudreaux/cc-plugin-product-strategist --skill product-launch-opsgit clone --depth 1 https://github.com/tjboudreaux/cc-plugin-product-strategistWrote 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/tjboudreaux/cc-plugin-product-strategist/product-launch-ops)<a href="https://agentmods.dev/skills/tjboudreaux/cc-plugin-product-strategist/product-launch-ops"><img src="https://agentmods.dev/badge/skills/tjboudreaux/cc-plugin-product-strategist/product-launch-ops/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/tjboudreaux/cc-plugin-product-strategist/product-launch-ops"><img src="https://agentmods.dev/badge/skills/tjboudreaux/cc-plugin-product-strategist/product-launch-ops.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.00025 | $0.00327 |
| Opus 5 | $0.00013 | $0.00163 |
| Sonnet 5 | $0.00005 | $0.00065 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
product-launch-ops 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 12d 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.
What it actually says
Launch and Learning Ops
Intent
- Treat every launch (soft, region, platform, season) as a scientific learning loop.
- Synchronize comms, community, growth, and product telemetry to reach PMF faster.
Inputs
- Target segments + messaging hierarchy.
- Channel plan (owned, earned, paid, influencer, platform features, on-chain activations).
- Experiment tracking template + analytics stack.
Workflow
- Hypothesis-driven launch plan
- Define explicit hypotheses for acquisition, activation, and retention per cohort.
- Map leading indicators and success/fail guardrails.
- Sequential rollout design
- Stage launches (friends & family → closed beta → open beta → public) with clear exit criteria.
- Prepare rollback + comms contingencies for each stage.
- Execution war room
- Establish daily/weekly rhythm: signal review, issue triage, community feedback digestion.
- Document decisions and pivots in a shared log.
- Learning harvest & handoff
- Produce launch retros with metric deltas, qualitative feedback, and next experiments.
- Update strategic roadmap / PMF scorecard accordingly.
Verification
- Launch brief, dashboard links, and experiment log stored in shared space before kickoff.
- Guardrails monitored in near real time; incident response plan tested.
- Retrospective completed within one week of stage completion with owners for next steps.
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.
- 12d ago First seen · 35 lines · 25 tokens per session scan A 5f3f5c04df25
product-launch-ops is a skill published in the GitHub repository tjboudreaux/cc-plugin-product-strategist (2 stars, last pushed 7mo ago), licensed MIT. It adds 25 tokens to every session and 327 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…