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 getagentseal/founder-playbook --skill four-stepsgit clone --depth 1 https://github.com/getagentseal/founder-playbookWrote 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/getagentseal/founder-playbook/four-steps)<a href="https://agentmods.dev/skills/getagentseal/founder-playbook/four-steps"><img src="https://agentmods.dev/badge/skills/getagentseal/founder-playbook/four-steps/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/getagentseal/founder-playbook/four-steps"><img src="https://agentmods.dev/badge/skills/getagentseal/founder-playbook/four-steps.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- 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.00148 | $0.06781 |
| Opus 5.5 | $0.00059 | $0.02712 |
| Sonnet 5.5 | $0.00030 | $0.01356 |
| Haiku 4.5 | $0.00015 | $0.00678 |
Grade A, and why
four-steps 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 1mo 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 — 569 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Note: This skill is independent analysis and commentary, not a reproduction of the original text. It synthesizes the book's core ideas with modern startup practice, surfaces where frameworks are outdated or incomplete, and integrates perspectives from adjacent disciplines. For the full argument and context, read the original book.
The Four Steps to the Epiphany
"Startups that survive the first few tough years do not follow the traditional product-centric launch model. Through trial and error, hiring and firing, successful startups all invent a parallel process to product development. I call this process 'Customer Development.'" - Steve Blank
Should You Use This Skill?
Are you searching for customers and a business model (not executing a known one)?
├─ YES → This skill is for you
└─ NO → You have paying customers and a repeatable sales process?
├─ YES, but stuck before mainstream → Use Crossing the Chasm
├─ YES, scaling fine → You're past this. Use Company Building concepts only
└─ NO, still pre-product → Start here at Customer Discovery
Have you validated that people will pay for your product?
├─ NO → Start at Customer Discovery (Step 1)
└─ YES → Can you describe a repeatable sales process?
├─ NO → You're in Customer Validation (Step 2)
└─ YES → Have you matched your launch to your Market Type?
├─ NO → You're in Customer Creation (Step 3)
└─ YES → Company Building (Step 4)
The Core Insight
9 out of 10 new product introductions fail. Not because the products don't work - because the companies never found customers.
The Product Development model (Concept → Build → Test → Launch) was designed for manufacturing in the early 1900s and adopted by consumer packaged goods in the 1950s. It works when you're launching a new product into an existing market with known customers. Most startups have neither.
PRODUCT DEVELOPMENT (what everyone does):
Concept/Seed ──→ Product Dev ──→ Alpha/Beta ──→ Launch
↑
"Where are the
customers?"
CUSTOMER DEVELOPMENT (what winners do - in parallel):
┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐
│ Customer │←──→│ Customer │←──→│ Customer │───→│ Company │
│ Discovery│ │Validation│ │ Creation │ │ Building │
└──────────┘ └──────────┘ └──────────┘ └──────────┘
↻ ↻ ↻
iterate iterate iterate
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 569 lines · 148 tokens per session scan A afa0e5aea118
four-steps is a skill published in the GitHub repository getagentseal/founder-playbook (780 stars, last pushed 21d ago), licensed MIT. It adds 148 tokens to every session and 6,781 once invoked, about $0.0006 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-30.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…