launch-strategy

launch-strategy is a skill for Claude Code, Codex from Maudeunfledged834/startup-founder-skills. It costs 41 tokens per session (2,010 once invoked), scanned A, a copy of launch-strategy, MIT.

A guide for planning a product launch, including the content, sales process, timing, partners, and offer around a new product, course, program, or major feature.

In plain words
What is it for?
Use it to plan pre-launch content, sales funnels, limited cart-opening and closing periods, affiliate or joint-venture launches, and evergreen funnels. It can also help shape pricing, bonuses, guarantees, testimonials, and other launch materials.
Why use it?
It helps organize a launch around a clear offer, audience, timeline, and sales path. It also helps choose between a one-time launch, a partner-supported launch, or an automated launch that runs continuously.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to plan pre-launch content, sales funnels, limited cart-opening and closing periods, affiliate or joint-venture launches, and evergreen funnels. It can also help shape pricing, bonuses, guarantees, testimonials, and other launch materials.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/maudeunfledged834/startup-founder-skills/launch-strategy
Install

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.

Any agent
npx skills add Maudeunfledged834/startup-founder-skills --skill launch-strategy
Clone the repo
git clone --depth 1 https://github.com/Maudeunfledged834/startup-founder-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for launch-strategy

README.md
[![agentmods](https://agentmods.dev/badge/skills/maudeunfledged834/startup-founder-skills/launch-strategy/github.svg)](https://agentmods.dev/skills/maudeunfledged834/startup-founder-skills/launch-strategy)
Your own site
<a href="https://agentmods.dev/skills/maudeunfledged834/startup-founder-skills/launch-strategy"><img src="https://agentmods.dev/badge/skills/maudeunfledged834/startup-founder-skills/launch-strategy/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.

agentmods 80×15 button for launch-strategy

Your own site · 80×15
<a href="https://agentmods.dev/skills/maudeunfledged834/startup-founder-skills/launch-strategy"><img src="https://agentmods.dev/badge/skills/maudeunfledged834/startup-founder-skills/launch-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,010 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00041 $0.02010
Opus 5 $0.00020 $0.01005
Sonnet 5 $0.00008 $0.00402
Haiku 4.5 $0.00004 $0.00201

Measured 11d ago against content hash 9c4b45aeb6d9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

launch-strategy 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 11d 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.

Origin

This is a copy

100% identical to launch-strategy — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/launch-strategy/SKILL.md · 109 lines

How it starts

The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Launch Strategy

When to Use

  • Planning a launch for a new product, course, program, or major feature.
  • Designing a pre-launch content sequence to build anticipation and desire.
  • Structuring a launch funnel with cart open/close mechanics.
  • Preparing a JV/affiliate launch with partner recruitment.
  • Building an evergreen launch funnel for ongoing automated sales.
  • Deciding between seed launch, internal launch, JV launch, or evergreen launch.
  • Applying the Product Launch Formula or similar sequenced launch methodology.

Context Required

  • From startup-context: product description, target audience, value proposition, existing audience size, email list size and engagement, brand voice.
  • From the user: what is being launched and the core transformation it provides, launch type (seed, internal, JV, evergreen), launch timeline and cart open/close dates, pricing and offer stack (product + bonuses + guarantee), existing assets (testimonials, case studies, content), budget for ads or affiliate commissions, team capacity, and any previous launch experience.

Workflow

  1. Define the offer — Clarify exactly what is being sold, the transformation it provides, the price point, and the offer stack (main product + bonuses). Total perceived value should be 10x+ the price.
  2. Select the launch type — Based on audience size, product maturity, and goals:
    • Seed Launch — Small list, new product. Validate and get testimonials before going big.
    • Internal Launch — Launch to your own list with a full pre-launch content sequence.
    • JV Launch — Partner with affiliates who promote to their lists for broader reach.
    • Evergreen Launch — Automated version of a live launch, triggered by opt-in.
  3. Build the launch list — Create a dedicated opt-in to identify the most interested prospects. This is your hottest segment. Build this list before creating pre-launch content.
  4. Create pre-launch content (PLC) — Develop 3-4 pieces of high-value content using the Sideways Sales Letter structure (see framework below). Each piece delivers standalone value while advancing the sale.
  5. Write the launch email sequence — Plan emails for every phase: PLC releases, cart open announcement, mid-launch social proof, final push urgency, and cart close deadline.
  6. Build the sales page — Create the sales page with offer stack, testimonials, guarantee, and countdown timer. The page should make the buying decision feel obvious.
  7. Recruit JV partners (if applicable) — Reach out to potential affiliates 4-6 weeks before launch. Provide swipe files, tracking links, and leaderboard incentives.
  8. Execute the launch — Release PLCs on schedule, open cart, send emails, engage with prospects in real time. Most sales happen in the last 24 hours.
  9. Close the cart and debrief — When the cart closes, it closes. Follow up with non-buyers. Analyze results and plan improvements for the next launch.

Read the full file on GitHub · 109 lines

Changes

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.

  1. 11d ago First seen · 109 lines · 41 tokens per session scan A 9c4b45aeb6d9

Subscribe to this mod's changes

launch-strategy is a skill published in the GitHub repository Maudeunfledged834/startup-founder-skills (6 stars, last pushed 2d ago), licensed MIT. It adds 41 tokens to every session and 2,010 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to launch-strategy, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

create-site

Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…

microsoft/power-platform-skills · 73 tokens

deploy-site

Deploys an existing Power Pages code site to a Power Pages environment using PAC CLI. Handles tooling verification, authentication, environment confirmation, building, and uploading. Use when the user wants to deploy, upload, or publish their code site.

microsoft/power-platform-skills · 50 tokens

add-teams

Adds Microsoft Teams connector to a Power Apps code app. Use when sending Teams messages, posting to channels, or integrating with Teams chat.

microsoft/power-platform-skills · 31 tokens

elixir-idioms

OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.

oliver-kriska/claude-elixir-phoenix · 44 tokens

tidewave-integration

Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.

oliver-kriska/claude-elixir-phoenix · 38 tokens

security

Enforce Elixir/Phoenix security — auth, OAuth, sessions, CSRF, XSS, SQL injection, input validation, secrets. Use when editing auth files, login flows, RBAC, or API keys.

oliver-kriska/claude-elixir-phoenix · 47 tokens