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 marcos-sponton/frameworks-as-skills --skill demand-side-salesgit clone --depth 1 https://github.com/marcos-sponton/frameworks-as-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/marcos-sponton/frameworks-as-skills/demand-side-sales)<a href="https://agentmods.dev/skills/marcos-sponton/frameworks-as-skills/demand-side-sales"><img src="https://agentmods.dev/badge/skills/marcos-sponton/frameworks-as-skills/demand-side-sales/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/marcos-sponton/frameworks-as-skills/demand-side-sales"><img src="https://agentmods.dev/badge/skills/marcos-sponton/frameworks-as-skills/demand-side-sales.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.00282 | $0.03219 |
| Opus 5 | $0.00141 | $0.01610 |
| Sonnet 5 | $0.00056 | $0.00644 |
| Haiku 4.5 | $0.00028 | $0.00322 |
Grade A, and why
demand-side-sales 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Demand-Side Sales
Bob Moesta's demand-side approach to sales, product, and innovation — distilled from Demand-Side Sales 101 (2020, w/ Greg Engle), Learning to Build (2022), Job Moves (2024, w/ Ethan Bernstein + Michael Horn), the earlier work with Clayton Christensen culminating in Competing Against Luck (2016), the Re-Wired Group's client work, The Circuit Breaker podcast (w/ Greg Engle), dense podcast appearances including Lenny Rachitsky (2023, 2025), Intercom, Business of Software, and INDUSTRY 2025, plus the canonical JTBD method library at jobstobedone.org (w/ Chris Spiek).
This skill helps you do the thing Moesta spends most of his airtime insisting on: flip from supply-side ("how do we sell better?") to demand-side ("why do people buy?"). The method centers on understanding the forces that cause someone to switch from their current solution to a new one — not features, not demographics, not funnels. Forces, timelines, struggling moments, and the progress the customer is trying to make.
When this skill activates
Use this skill when the user is:
- Trying to understand why customers buy, switch, churn, or stay — the causal story, not the correlation.
- Designing or redesigning a sales process around how people actually buy (not how you want to sell).
- Planning, running, or analyzing Switch Interviews to reconstruct a purchase timeline.
- Mapping the Four Forces of Progress on a real buying decision or product adoption.
- Wondering why customers aren't switching to a superior product (usually: Anxiety and Habit are winning).
- Evaluating whether to add features (which often increases Anxiety instead of Pull).
- Redesigning marketing, onboarding, or customer success around the buying timeline stages.
- Trying to identify the real competition (which is rarely who you think — Casper vs. ZzzQuil, not Casper vs. Tempur-Pedic).
- Running demand-side analysis for a new product launch without existing customers.
- Applying JTBD to career decisions, hiring, or talent management (Job Moves territory).
What ships with it
12 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.
- evals/evals.json 7.9 KB
- examples/.gitkeep 0 B
- README.md 6.8 KB
- references/applications.md 10 KB
- references/author-live-sources.md 10 KB
- references/examples.md 14 KB
- references/heuristics.md 12 KB
- references/method.md 14 KB
- references/post-book.md 12 KB
- references/prompts.md 9.2 KB
- references/sources.md 9.1 KB
- references/voice-and-tone.md 14 KB
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 · 123 lines · 282 tokens per session scan A 8adfb0f46508
demand-side-sales is a skill published in the GitHub repository marcos-sponton/frameworks-as-skills (1 stars, last pushed 1mo ago), licensed MIT. It adds 282 tokens to every session and 3,219 once invoked, about $0.0014 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
acquire-skills
Find and install skills for what you're doing — tech or reasoning gaps. Matches activity and tech context to relevant skills. Use when entering unfamiliar tech, stuck on a reasoning challenge, or no skill fits.
find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
endpoint-discovery
Discovers URLs, endpoints, and paths from web applications using katana, gospider, and gau. Use when needing to enumerate application endpoints, find hidden paths, gather historical URLs, or map web application structure during reconnaissance.
param-miner
Discover hidden HTTP parameters in web applications that could reveal hidden functionality or vulnerabilities. Use when testing APIs, when looking for hidden parameters like admin or debug, or when the user mentions parameter discovery.
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
daily-paper-generator
Use when the user asks to generate daily paper digests on a general topic. This skill supports both arXiv and bioRxiv (or either one), then produces structured Chinese/English summaries for selected papers.