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 agentmods add skills/danecwalker/agentskills/saas-playbooknpx skills add danecwalker/agentskills --skill saas-playbookgit clone --depth 1 https://github.com/danecwalker/agentskillsWrote 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/danecwalker/agentskills/saas-playbook)<a href="https://agentmods.dev/skills/danecwalker/agentskills/saas-playbook"><img src="https://agentmods.dev/badge/skills/danecwalker/agentskills/saas-playbook.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 | $0.00130 | $0.02383 |
| Opus 5 | $0.00065 | $0.01192 |
| Sonnet 5 | $0.00026 | $0.00477 |
| Haiku 4.5 | $0.00013 | $0.00238 |
Grade A, and why
saas-playbook 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 5d 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/saas-playbook — Build a SaaS the boring, working way
Source of the method: How I'd Build a SaaS in 2026 — Shayan Taslim, UserJot
The default failure mode of a technical founder is building a well-engineered product nobody was already trying to pay for. This skill exists to keep the work pointed at demand, distribution, and revenue — and to keep the codebase small enough to change every week.
Usage
/saas-playbook <idea, market, or current situation>
/saas-playbook validate <idea>
/saas-playbook scope <idea> # cut to a shippable MVP
/saas-playbook price <product>
/saas-playbook triage <feature requests>
/saas-playbook next # what to work on this week
If the user gives only a vague idea, run Phase 1 first. Never jump to architecture or stack selection before demand evidence exists.
The nine rules (never violate)
- Boring market with existing demand. Enter a category where people already pay and already complain. Do not invent a category.
- Talk to customers constantly. Every user is worth more than their MRR — they carry context, edge cases, and the next feature.
- No big launch. Launch day is not a growth strategy. Ship-and-post beats weeks of prep for one artificial spike.
- Drip instead. Introduce the product continuously: progress posts, DMs, build-in-public. That compounds into trust.
- Keep the stack simple. Optimize for 10–50 users, not Netflix. No k8s, no bespoke CI, no microservices before product-market fit.
- Say no more than yes. Every yes is permanent support surface. Protect the core.
- Charge from day one. "Free while in beta" manufactures fake validation. Charge early and charge more than feels comfortable.
- Public feedback board on day one. Post → vote → in progress → shipped. It shapes the roadmap and signals responsiveness to prospects.
- Marketing > coding. Target split ≈ 50% marketing / 20% support / 30% building. A product nobody knows about has no quality.
What ships with it
6 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.
- 5d ago First seen · 241 lines · 130 tokens per session scan A 3a7f6e123cb6
saas-playbook is a skill published in the GitHub repository danecwalker/agentskills (2 stars, last pushed 11d ago), licensed MIT. It adds 130 tokens to every session and 2,383 once invoked, about $0.0006 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
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…