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.
git clone --depth 1 https://github.com/classicchins/compounding-marketingWrote 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/classicchins/compounding-marketing/cm-launch)<a href="https://agentmods.dev/commands/classicchins/compounding-marketing/cm-launch"><img src="https://agentmods.dev/badge/commands/classicchins/compounding-marketing/cm-launch/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/commands/classicchins/compounding-marketing/cm-launch"><img src="https://agentmods.dev/badge/commands/classicchins/compounding-marketing/cm-launch.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.00000 | $0.00363 |
| Opus 5.5 | $0.00000 | $0.00145 |
| Sonnet 5.5 | $0.00000 | $0.00073 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
cm-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 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.
What it actually says
/cm:launch — Launch Planning & Execution
Comprehensive launch planning from strategy to execution checklist.
What It Does
Plans a product or feature launch end-to-end with timeline, channels, and tactics.
Process
-
Define Launch Scope
- Ask: What are you launching? (product, feature, update)
- Ask: Launch date?
- Ask: Launch tier? (major, minor, update)
- Ask: Resources? (team, budget)
-
Run Launch Strategy Skill
- Execute
launch-strategyskill - Output: Launch timeline (8 weeks → launch day → 4 weeks post)
- Execute
-
Run GTM Strategy (if new product)
- Execute
gtm-strategyskill - Define PLG vs. sales-led motion
- Output: GTM strategy document
- Execute
-
Run Channel Strategy
- Execute
channel-strategyskill - Prioritize channels for launch
- Output: Channel plan with resources
- Execute
-
Create Launch Checklist
- Combine all outputs
- Assign owners to tasks
- Set deadlines
- Identify risks
-
Provide Launch Plan
- Unified launch document
- Timeline with milestones
- Channel tactics
- Success metrics
When to Use
- Launching new product
- Major feature release
- Entering new market
- Rebranding
Prerequisites
- Positioning defined (run
/cm:positionif needed) - Product ready (or launch date set)
Time Investment
2-3 hours
Output
- Complete launch plan
- Timeline with owners
- Channel plan
- Success metrics
- Risk mitigation plan
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 · 66 lines · 0 tokens per session scan A 1b4ac351122e
cm-launch is a command published in the GitHub repository classicchins/compounding-marketing (8 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 363 tokens. 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.
cm-launch compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| cm-launchclassicchins/compounding-marketing | Command | 8 | 5mo ago | MIT | A | 0 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |