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/brainbytes-dev/everything-claude-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/brainbytes-dev/everything-claude-marketing/launch)<a href="https://agentmods.dev/commands/brainbytes-dev/everything-claude-marketing/launch"><img src="https://agentmods.dev/badge/commands/brainbytes-dev/everything-claude-marketing/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/brainbytes-dev/everything-claude-marketing/launch"><img src="https://agentmods.dev/badge/commands/brainbytes-dev/everything-claude-marketing/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.00025 | $0.01770 |
| Opus 5.5 | $0.00010 | $0.00708 |
| Sonnet 5.5 | $0.00005 | $0.00354 |
| Haiku 4.5 | $0.00003 | $0.00177 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/launch
Plan a complete product or feature launch from strategy through execution, covering GTM approach, messaging, channel plans, timeline, and cross-functional coordination.
What This Command Does
The /launch command produces a comprehensive launch plan that aligns marketing, product, sales, and customer success around a coordinated go-to-market effort. It goes beyond marketing tactics to address the full launch lifecycle: pre-launch preparation, launch day execution, and post-launch optimization. The output is a plan your team can immediately begin executing against.
The command delegates primarily to the product-marketer agent, which orchestrates the GTM strategy. For execution-level details, it draws on the strategist, copywriter, and pr-specialist agents as needed.
When to Use
- You are launching a new product and need a full GTM plan
- You are shipping a major feature and want a coordinated launch effort
- You are entering a new market or segment with an existing product
- You need to coordinate a launch across multiple teams (marketing, sales, product, CS)
- You are planning a rebrand, pricing change, or other significant market-facing event
- You want a tiered launch plan (beta, soft launch, general availability)
How It Works
- Launch Assessment — Evaluates the launch scope, audience impact, and strategic importance to determine the right launch tier
- Messaging Development — Creates the core positioning, value proposition, and messaging hierarchy for the launch
- Channel Strategy — Selects and prioritizes marketing channels based on audience, budget, and launch tier
- Timeline Construction — Builds a phased timeline with pre-launch, launch day, and post-launch milestones
- Asset Planning — Lists all required assets (landing pages, emails, blog posts, sales collateral, etc.) with owners and deadlines
- Cross-Functional Coordination — Defines what each team needs to do and when
- Success Metrics — Establishes KPIs and a measurement plan for evaluating launch impact
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 · 175 lines · 25 tokens per session scan A f6575f66333e
launch is a command published in the GitHub repository brainbytes-dev/everything-claude-marketing (10 stars, last pushed 7mo ago), licensed MIT. It adds 25 tokens to every session and 1,770 once invoked, about $0.0001 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.
launch compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| launchbrainbytes-dev/everything-claude-marketing | Command | 10 | 7mo ago | MIT | A | 25 | 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 |