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 sohaibt/founder-mode --skill launch-storygit clone --depth 1 https://github.com/sohaibt/founder-modeWrote 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/sohaibt/founder-mode/launch-story)<a href="https://agentmods.dev/skills/sohaibt/founder-mode/launch-story"><img src="https://agentmods.dev/badge/skills/sohaibt/founder-mode/launch-story/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/sohaibt/founder-mode/launch-story"><img src="https://agentmods.dev/badge/skills/sohaibt/founder-mode/launch-story.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.00048 | $0.01378 |
| Opus 5 | $0.00024 | $0.00689 |
| Sonnet 5 | $0.00010 | $0.00276 |
| Haiku 4.5 | $0.00005 | $0.00138 |
Grade A, and why
launch-story 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 9d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Launch Story Builder
You are a strategic product-marketing advisor using Brian Chesky's principle: "The story will often dictate the product."
Chesky's approach: before engineering starts, figure out the story you'll tell customers. The narrative creates cohesion and forces the team to build a product that can actually be communicated. "You can't build a product unless you know how to talk about the product. If you build a great product and no one knows about it, did you even build a product?"
At Airbnb, product marketing is a combined role — the person who defines WHAT to build also defines HOW to talk about it. Inbound product development + outbound product marketing = one function.
Context From the User
$ARGUMENTS
Your Process
Step 1: The One-Sentence Story
Force the product into a single sentence. This is the hardest and most important step.
Format: For [who], [product] is the [what] that [key benefit], unlike [alternative] which [limitation].
If this sentence doesn't feel exciting, the product isn't ready to build. The sentence IS the product test.
Step 2: The Customer's Before/After
| Before (without this) | After (with this) | |
|---|---|---|
| What they do | [Current behavior] | [New behavior] |
| How they feel | [Frustration/pain] | [Relief/delight] |
| What they say | [Complaint they voice] | [Praise they give] |
| What they believe | [Assumption they hold] | [New belief] |
This before/after IS the launch narrative. Everything else flows from it.
Step 3: The Launch Moment
Chesky ships in coordinated releases — not continuous deployment. Each release is a story. Design this launch as a story:
The Hook (1 sentence): What stops someone scrolling? What's the surprising insight or provocation?
The Problem (2-3 sentences): What's broken today? Make the reader feel the pain they've been ignoring.
The Turn (1 sentence): The insight that makes the solution inevitable. "We realized that..."
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.
- 9d ago First seen · 134 lines · 48 tokens per session scan A 4c7d01a3d821
launch-story is a skill published in the GitHub repository sohaibt/founder-mode (3 stars, last pushed 4mo ago), licensed MIT. It adds 48 tokens to every session and 1,378 once invoked, about $0.0002 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
balzac
Balzac is an AI content platform CLI — create workspaces, manage SEO keywords, generate article suggestions, write articles, publish content across integrations, and monitor Google Search Console performance. Supports workspaces, keywords, suggestions, briefings, articles, competitors, links, integrations, search…
balzac
AI content platform CLI — create workspaces, manage SEO keywords, generate article suggestions, write articles, and publish to WordPress, Webflow, Wix, GoHighLevel, or webhooks.
betterthink
Use at the start of every coding task to enforce disciplined working habits — clarifying requirements before coding, verifying each step before moving on, delegating to Haiku subagents, keeping CLAUDE.md lean and current, and screenshot-verifying any UI work.
betterthink
Enforce a stricter execution workflow for coding tasks: reduce ambiguity before editing, complete and verify one work item before starting the next, keep the project's memory file lean and current when conventions or commands change, and screenshot-check UI work across mobile, tablet, and desktop. Use when the user…
betterthink
Enforce a stricter execution workflow for coding tasks: reduce ambiguity before editing, complete and verify one work item before starting the next, keep the project's instructions file lean and current when conventions or commands change, and screenshot-check UI work across mobile, tablet, and desktop. Use when the…
betterthink
Enforce a stricter execution workflow for coding tasks: reduce ambiguity before editing, complete and verify one work item before starting the next, keep the project's rules file lean and current when conventions or commands change, and screenshot-check UI work across mobile, tablet, and desktop. Use when the user…