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 made-to-stickgit 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/made-to-stick)<a href="https://agentmods.dev/skills/getagentseal/founder-playbook/made-to-stick"><img src="https://agentmods.dev/badge/skills/getagentseal/founder-playbook/made-to-stick/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/made-to-stick"><img src="https://agentmods.dev/badge/skills/getagentseal/founder-playbook/made-to-stick.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 83 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00182 | $0.03560 |
| Opus 5 | $0.00091 | $0.01780 |
| Sonnet 5 | $0.00036 | $0.00712 |
| Haiku 4.5 | $0.00018 | $0.00356 |
Grade A, and why
made-to-stick 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 12d 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 — 249 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.
Made to Stick
"There is no such thing as an inherently uninteresting subject. There are only uninterested communicators." - Chip Heath & Dan Heath
Should You Use This Skill?
Is your message failing to land?
|-- YES --> Do people understand it but forget it?
| |-- YES --> Probably missing CONCRETE or STORIES. Check those principles.
| +-- NO --> Do people tune out before hearing it?
| |-- YES --> Missing UNEXPECTED (no hook) or SIMPLE (too complex).
| +-- NO --> Do they hear it but not care?
| |-- YES --> Missing EMOTIONAL. They believe but don't act.
| +-- NO --> Do they care but not believe it?
| |-- YES --> Missing CREDIBLE.
| +-- NO --> THIS SKILL. Run the full diagnostic.
+-- NO --> Is the message landing but people aren't acting?
|-- YES --> Missing STORIES (no mental simulation of action) or
| EMOTIONAL (they believe but don't feel).
+-- NO --> The message is working. Don't fix what isn't broken.
The Core Insight
The enemy of sticky messages is the Curse of Knowledge.
Once you know something, you can't imagine not knowing it. You tap a song on a table and think it's obvious - but listeners guess correctly only 2.5% of the time (you predicted 50%). This is the tappers-and-listeners experiment, and it's the central metaphor of the entire book.
Every expert, every founder, every leader suffers from this curse. It makes you talk in abstractions when your audience needs concrete details. It makes you assume shared context that doesn't exist. It makes your messages forgettable.
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.
- 12d ago First seen · 249 lines · 182 tokens per session scan A 79076406b24f
made-to-stick is a skill published in the GitHub repository getagentseal/founder-playbook (570 stars, last pushed 1mo ago), licensed MIT. It adds 182 tokens to every session and 3,560 once invoked, about $0.0009 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…
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…