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 whawkinsiv/solo-founder-skills --skill launchgit clone --depth 1 https://github.com/whawkinsiv/solo-founder-skillsWrote 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/whawkinsiv/solo-founder-skills/launch)<a href="https://agentmods.dev/skills/whawkinsiv/solo-founder-skills/launch"><img src="https://agentmods.dev/badge/skills/whawkinsiv/solo-founder-skills/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/skills/whawkinsiv/solo-founder-skills/launch"><img src="https://agentmods.dev/badge/skills/whawkinsiv/solo-founder-skills/launch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00068 | $0.02360 |
| Opus 5 | $0.00034 | $0.01180 |
| Sonnet 5 | $0.00014 | $0.00472 |
| Haiku 4.5 | $0.00007 | $0.00236 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Launch Strategy & Go-to-Market
A launch is not a moment — it's a 6-week campaign with a peak in the middle. This skill helps you build a waitlist, coordinate launch day across multiple channels, and sustain momentum for 30 days after.
Core Principles
- A launch without an audience is a tree falling in an empty forest. Build the audience first, even if it's small.
- Momentum is manufactured, not organic. Every "overnight success" launch had weeks of preparation.
- Launch once, but launch everywhere simultaneously. Coordinated beats sequential.
- The goal of launch day is not revenue — it is attention, feedback, and a base of early advocates.
- Post-launch matters more than launch day. Most founders celebrate and then go silent. The ones who win keep pushing for 30 days after.
Pre-Launch Phase (4-6 Weeks Before)
Build a Waitlist
Waitlist Setup Checklist:
- [ ] Landing page live with clear value prop (see landing-page)
- [ ] Email capture with incentive ("Get early access" or "Join 500+ founders")
- [ ] Confirmation email with share mechanic ("Move up the list by sharing")
- [ ] Weekly update email to keep waitlist warm
- [ ] Social proof counter ("1,247 founders waiting")
Tools: Waitlist-specific (LaunchList, GetWaitlist) or simple email capture (ConvertKit, Buttondown).
Tell AI:
Build a waitlist landing page for [product]. Include email capture,
a "why join" section with 3 bullets, social proof counter, and a
share-to-move-up mechanic. Use [framework/stack].
Seed Your Launch Audience
You need at least 100 people who will show up on launch day. Sources:
- Build in public — Share progress on Twitter/X, LinkedIn, Indie Hackers for 4-6 weeks before launch (see content)
- Direct outreach — Email 50 people who fit your ICP, offer early access in exchange for feedback
- Communities — Be active (not spammy) in 3-5 communities where your users hang out
- Personal network — Email everyone you know. Ask for shares, not signups
- Founder communities — Indie Hackers, r/SaaS, Hacker News, relevant Discord/Slack groups
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.
- 11d ago First seen · 247 lines · 68 tokens per session scan A a1a23fcb5fe5
launch is a skill published in the GitHub repository whawkinsiv/solo-founder-skills (243 stars, last pushed 15d ago), licensed MIT. It adds 68 tokens to every session and 2,360 once invoked, about $0.0003 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-30.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…