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 uthumany/uthy-legacy-os --skill jobs-to-be-donegit clone --depth 1 https://github.com/uthumany/uthy-legacy-osWrote 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/uthumany/uthy-legacy-os/jobs-to-be-done)<a href="https://agentmods.dev/skills/uthumany/uthy-legacy-os/jobs-to-be-done"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/jobs-to-be-done/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/uthumany/uthy-legacy-os/jobs-to-be-done"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/jobs-to-be-done.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.00033 | $0.01056 |
| Opus 5.5 | $0.00013 | $0.00422 |
| Sonnet 5.5 | $0.00007 | $0.00211 |
| Haiku 4.5 | $0.00003 | $0.00106 |
Grade A, and why
jobs-to-be-done 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 2mo 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jobs-to-be-Done (JTBD)
Overview
The Jobs-to-be-Done framework shifts focus from who the user is (demographics) to what they're trying to accomplish. People "hire" products to do jobs in their life. This skill helps you identify functional, emotional, and social jobs → design products that get hired, not features that gather dust.
When to Use
- Understanding why users choose your product (or a competitor's)
- Identifying unmet needs in a market
- Defining product strategy and positioning
- Evaluating new feature ideas against core user jobs
- Don't use for: incremental UI improvements, bug prioritization, or compliance work
Instructions
1. Identify the Job Statement
Use the format: When [situation], I want to [motivation] so I can [desired outcome].
Example: "When I'm assigned a new project, I want to understand what's already been decided so I can avoid redoing work."
Break it into three parts:
- Situation: When does this job arise?
- Motivation: What does the user want to do?
- Outcome: What's the end goal?
2. Uncover the Job Dimensions
Every job has three layers:
- Functional: What the user wants to accomplish (the task)
- Emotional: How the user wants to feel (confident, relieved, proud)
- Social: How the user wants to be perceived (competent, innovative, reliable)
Ask: "When this job is done well, how does it make you feel? How do others see you?"
3. Map the Job-to-be-Done Timeline
Jobs don't exist in isolation. Map the full process:
- Define — What triggers the job?
- Locate — What information do they need?
- Prepare — What do they need to set up?
- Confirm — How do they know it's working?
- Execute — The core job
- Monitor — How do they track success?
- Modify — What adjustments do they make?
- Conclude — How do they finish?
4. Identify Needs at Each Step
For each step, ask:
- What's frustrating about this step?
- What workaround have you created?
- If you could wave a magic wand, what would happen?
- What makes you abandon this process?
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.
- 2mo ago First seen · 109 lines · 33 tokens per session scan A 7e62c74570e3
jobs-to-be-done is a skill published in the GitHub repository uthumany/uthy-legacy-os (5 stars, last pushed 5mo ago), licensed MIT. It adds 33 tokens to every session and 1,056 once invoked, about $0.0001 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-31.
jobs-to-be-done compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| jobs-to-be-doneuthumany/uthy-legacy-os | Skill | 5 | 5mo ago | MIT | A | 33 | Claude Code, Codex |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | today | MIT | A | 200 | Claude Code, Codex |
| playwright-climicrosoft/playwright | Skill | 99k | today | Apache-2.0 | A | 19 | Claude Code |
| systematic-debuggingobra/superpowers | Skill | 314k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |
| chat-pet-sprite-creationmicrosoft/vscode | Skill | 195k | today | MIT | A | 53 | Claude Code, Codex |