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 RBraga01/builder-growth --skill launch-plan-designgit clone --depth 1 https://github.com/RBraga01/builder-growthWrote 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/rbraga01/builder-growth/launch-plan-design)<a href="https://agentmods.dev/skills/rbraga01/builder-growth/launch-plan-design"><img src="https://agentmods.dev/badge/skills/rbraga01/builder-growth/launch-plan-design.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.1 | $0.00075 | $0.01756 |
| Opus 5 | $0.00037 | $0.00878 |
| Sonnet 5 | $0.00015 | $0.00351 |
| Haiku 4.5 | $0.00007 | $0.00176 |
Grade A, and why
launch-plan-design 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 7d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Launch Plan Design
The Law
A LAUNCH WITHOUT A ROLLBACK CRITERION IS A COMMITMENT, NOT A TEST.
"We'll figure out launch day as we go" means the first time anyone decides what "going badly" looks like is in the middle of it going badly.
Goal + audience + offer + assets + channels + timeline + pre/launch/post tasks + metrics + risks + rollback criteria IS a launch plan.
When to Use
Trigger before:
- Launching any new product, feature, or campaign to an external audience
- Re-launching after a significant pause, rebrand, or pivot
- Any coordinated multi-channel push (PR, paid, social, email, partners) with a fixed go-live date
- Any time
growth-strategy-designandoffer-quality-gatehave produced an approved strategy and offer that now need a go-to-market plan
When NOT to Use
- Continuous, ungated rollouts with no fixed launch moment (e.g., gradual feature flag rollout with no external announcement)
- Internal-only releases with no external audience or campaign attached
The Twelve Launch Elements
A complete launch plan defines all twelve before launch day, not during it.
1 — Launch Goal
The single outcome this launch is meant to produce — tied to the north star metric from growth-strategy-design. One goal; a launch optimising for press coverage, signups, and revenue simultaneously will not be evaluated cleanly against any of them.
2 — Audience
Who this launch reaches first — typically the segment from the strategy, possibly narrowed further for a phased rollout.
3 — Offer
The validated offer from offer-quality-gate this launch is built around.
4 — Launch Assets
Every asset required: landing page, demo video, press kit, social posts, email sequence, sales collateral. Named and owned, not assumed to "come together."
5 — Channels
The channels this launch will use, from channel-selection-audit — primary and any secondary channels activated specifically for launch (e.g., a one-time press push that is not an ongoing channel).
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.
- 7d ago First seen · 169 lines · 75 tokens per session scan A 3e17adfe4d80
launch-plan-design is a skill published in the GitHub repository RBraga01/builder-growth (2 stars, last pushed 2mo ago), licensed MIT. It adds 75 tokens to every session and 1,756 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-08-31.
Other skills, from other repositories
gr-geo-cite
A guide for checking whether AI assistants such as ChatGPT, Claude, Perplexity, and Gemini mention or cite your website when answering set questions.
gingiris-github-star-growth
A guide to steadily increasing the number of people who bookmark an open-source project on GitHub by building content, community, events, contributors, and ambassadors.
gr-blog-post
A Jekyll blog publishing workflow. Jekyll is a tool that turns text and templates into a website, and this workflow also prepares matching English, Japanese, and Korean posts.
gr-seo-patrol
An automated SEO and GEO checking routine. SEO helps pages appear in search engines; GEO checks how they may be found and understood by AI-based search tools.
gingiris-reddit-marketing
🇺🇸 Reddit Marketing & Growth Playbook 2026 — The complete Reddit operations SOP for AI/SaaS founders. Covers account warming (Karma 0→500 in 20 days), shadow ban prevention, multi-account matrix via fingerprint browsers, subreddit selection across 10K+ communities, content templates (90/10 rule), Product Hunt ×…
gingiris-growth-finder
Diagnose a product's growth model, stage, and current constraint, then route the request to the narrowest Gingiris specialist and execute it when installed. Use for broad or uncertain growth questions involving go-to-market, Product Hunt, GitHub stars, open-source marketing, B2B SaaS, PLG, ASO, SEO/GEO, AI citations…