Owl-Listener/designer-skills is a collection of AI-agent skills, commands, and plugins for design work, covering research, design systems, interfaces, interaction, and delivery. Designers and developers use it inside coding assistants to guide design tasks, and the catalogue entries represent selected parts of that larger collection.
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 Owl-Listener/designer-skills --skill jobs-to-be-donegit clone --depth 1 https://github.com/Owl-Listener/designer-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/owl-listener/designer-skills/jobs-to-be-done)<a href="https://agentmods.dev/skills/owl-listener/designer-skills/jobs-to-be-done"><img src="https://agentmods.dev/badge/skills/owl-listener/designer-skills/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/owl-listener/designer-skills/jobs-to-be-done"><img src="https://agentmods.dev/badge/skills/owl-listener/designer-skills/jobs-to-be-done.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00041 | $0.00364 |
| Opus 5 | $0.00020 | $0.00182 |
| Sonnet 5 | $0.00008 | $0.00073 |
| Haiku 4.5 | $0.00004 | $0.00036 |
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 13d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- jobs-to-be-done — 89% identical, 2 lines differ
What it actually says
Jobs-to-Be-Done
Map user Jobs-to-Be-Done to understand the deeper motivations behind user behavior.
Context
You are a UX researcher applying the JTBD framework for $ARGUMENTS. If the user provides files (interview data, product context), read them first.
Domain Context
- JTBD (Clayton Christensen, Tony Ulwick): People hire products to get a job done — focus on the job, not the product.
- Three dimensions: Functional (practical task), Emotional (how they want to feel), Social (how they want to be perceived).
- Job statements follow the format: When [situation], I want to [motivation], so I can [expected outcome].
Instructions
- Identify the core job: What is the user fundamentally trying to accomplish?
- Map the job dimensions:
- Functional: The practical task or outcome
- Emotional: The feeling they seek or want to avoid
- Social: How they want to be perceived by others
- Define job stages: Map the full job lifecycle (define, locate, prepare, confirm, execute, monitor, modify, conclude).
- Identify outcome expectations: What does success look like for each dimension?
- Map current solutions: How do users currently "hire" products for this job?
- Find opportunities: Where are current solutions underserving the job?
- Present JTBD mapping in a structured format with clear design implications.
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.
- 13d ago First seen · 32 lines · 41 tokens per session scan A f8c11b3c9a31
jobs-to-be-done is a skill published in the GitHub repository Owl-Listener/designer-skills (2,619 stars, last pushed 7d ago), licensed MIT. It adds 41 tokens to every session and 364 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
ui-review
Review UI code for StyleSeed design-system compliance, accessibility, mobile ergonomics, spacing discipline, and implementation quality.
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
node-inspect-debugger
See runtime state a console.log cannot reach — set real breakpoints, step, and dump the scope chain of a paused Node/TypeScript process. Use on "set a breakpoint", "inspect runtime state", "console.log isn't enough", "step through this", "what's in this closure at runtime", "attach a debugger". Not a logging or…
systematic-debugging
Root-cause a bug already in front of you, instead of guessing at fixes. Use on triggers like "root cause this", "why is this failing", "debug systematically", "this test is flaky", "it works locally but not in CI", or when a fix attempt has already failed once. Enforces a phased evidence-first process before any code…
code-quality
Drive static-analysis code quality in pi-agent-dashboard with Biome (analyze → fix → test), in changed-files or whole-repo mode. Use when asked to "improve code quality", "lint and fix", "clean up warnings", "fix Biome issues", "run static analysis", or when setting a code-quality goal. Skip for one-line edits.
autonomous-run
Prepare, start, inspect, resume, or stop a finite local overnight coding run after a human has accepted a Wayfinder terminal spec; coordinates a declared Claude/Codex maker and independent checker without pushing, merging, or writing to external systems.