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 kazdenc/builder-skills --skill jtbdgit clone --depth 1 https://github.com/kazdenc/builder-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/kazdenc/builder-skills/jtbd)<a href="https://agentmods.dev/skills/kazdenc/builder-skills/jtbd"><img src="https://agentmods.dev/badge/skills/kazdenc/builder-skills/jtbd/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/kazdenc/builder-skills/jtbd"><img src="https://agentmods.dev/badge/skills/kazdenc/builder-skills/jtbd.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.00049 | $0.00995 |
| Opus 5 | $0.00024 | $0.00498 |
| Sonnet 5 | $0.00010 | $0.00199 |
| Haiku 4.5 | $0.00005 | $0.00100 |
Grade A, and why
jtbd 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jobs to Be Done
When making product decisions, think in terms of the job someone is trying to get done — not the feature they're asking for, not the persona they fit, not the solution they currently use.
A job is a goal someone has independent of any product. People have been "listening to music" for centuries — the solutions change, the job doesn't. Ground every product decision in the job.
How to Think About It
┌─────────────────────────────────────────────┐
│ ASPIRATIONS │ Who they want to become
│ ┌───────────────────────────────────────┐ │
│ │ BIG JOBS │ │ The main objective
│ │ ┌─────────────────────────────────┐ │ │
│ │ │ LITTLE JOBS │ │ │ Steps within the job
│ │ │ ┌───────────────────────────┐ │ │ │
│ │ │ │ MICRO-JOBS │ │ │ │ Individual activities
│ │ │ └───────────────────────────┘ │ │ │
│ │ └─────────────────────────────────┘ │ │
│ └───────────────────────────────────────┘ │
└─────────────────────────────────────────────┘
Ask "why?" to move up. Ask "how?" to move down. The right altitude depends on what you're deciding — strategy lives at the top, feature design at the bottom.
Five Things to Separate
Always pull these apart. Mixing them leads to muddy thinking:
| Element | Ask | Keep it |
|---|---|---|
| Who — the performer | Who actually does this? | Separate from the buyer, the boss, the audience |
| What — the job | What are they trying to accomplish? | Functional. No solutions, no adjectives |
| How — the process | What stages do they move through? | Chronological. Beginning → done |
| Why — the needs | How do they measure success along the way? | Specific. Measurable. One need per statement |
| When/Where — circumstances | What context shapes how the job gets done? | Concrete. Time, place, constraints |
Writing Job Statements
Follow verb + object + clarifier. Think of an invisible "I want to..." in front.
What ships with it
5 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.
- 9d ago First seen · 79 lines · 49 tokens per session scan A 99b418c605cd
jtbd is a skill published in the GitHub repository kazdenc/builder-skills (45 stars, last pushed 6mo ago), licensed MIT. It adds 49 tokens to every session and 995 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-30.
Other skills, from other repositories
commercial-opportunity-review
Review Product, offering, catalog, quote, and sale evidence for commercial opportunities.
demand-triage
Prepare classification, evidence gaps, and score inputs for product demand without crossing the funding boundary.
investment-preparation
Prepare an evidence-linked product investment packet while preserving the governed funding decision.
outcome-review
Review whether a funded product bet changed its intended outcome and append evidence-backed learning.
product-line-performance-review
Roll real Product evidence into a ProductLine review without changing the canonical reporting boundary.
roadmap-refresh
Refresh Now, Next, and Later from funded demand, objectives, dependencies, and delivery evidence.