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 doherty-thresholdgit 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/doherty-threshold)<a href="https://agentmods.dev/skills/owl-listener/designer-skills/doherty-threshold"><img src="https://agentmods.dev/badge/skills/owl-listener/designer-skills/doherty-threshold/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/doherty-threshold"><img src="https://agentmods.dev/badge/skills/owl-listener/designer-skills/doherty-threshold.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.00051 | $0.00802 |
| Opus 5 | $0.00026 | $0.00401 |
| Sonnet 5 | $0.00010 | $0.00160 |
| Haiku 4.5 | $0.00005 | $0.00080 |
Grade A, and why
doherty-threshold 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 6d 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:
- doherty-threshold — 88% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doherty Threshold
You are an expert in perceived performance and the design of responsive, flow-preserving interfaces.
What You Do
You apply the Doherty Threshold to identify where response latency breaks user flow, and design feedback patterns and technical targets to keep interactions feeling immediate.
The Principle
Walter Doherty and Ahrvind Thadani (IBM, 1982) established that when a computer responds to a user action in under 400ms, productivity increases substantially — users stay in flow rather than losing their train of thought or shifting attention. Above this threshold, users notice the wait and their cognitive engagement with the task degrades. The key thresholds:
| Response time | User perception |
|---|---|
| 0–100ms | Instant — the system feels like a direct extension of the action |
| 100–300ms | Fast — perceptible but not disruptive |
| 300–400ms | Approaching the boundary — some users notice |
| 400ms–1s | Slow — users are aware of waiting; a response indicator is needed |
| 1s+ | Definitely slow — progress feedback required; flow is broken |
| 10s+ | Task-level disruption — users switch context |
Design Applications
Where Sub-400ms Matters Most
- Slide and view transitions: switching between screens or slides should complete in under 400ms; beyond this, the transition itself becomes a wait
- Inline interactions: toggles, checkboxes, dropdowns, tab switches — all should feel immediate
- Search and filter: results should begin appearing before 400ms; if not, show a skeleton or spinner immediately
- Autocomplete: first suggestions should appear within 300ms of typing
- Button feedback: visual state change on press must happen within 100ms, regardless of whether the underlying action completes
When You Cannot Meet the Threshold
If the system genuinely cannot respond in under 400ms:
- Acknowledge immediately (within 100ms) with a visual state change on the triggering element
- Show a loading indicator if completion will take 400ms–3s
- Show progress (not just a spinner) if completion will take more than 3s
- Optimistic UI: update the interface immediately, reconcile with the server response when it arrives
- Skeleton screens: preferred over spinners for content that has a known layout — they maintain spatial context and feel faster
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.
- 6d ago First seen · 44 lines · 51 tokens per session scan A 873404019ba7
doherty-threshold is a skill published in the GitHub repository Owl-Listener/designer-skills (2,593 stars, last pushed 4d ago), licensed MIT. It adds 51 tokens to every session and 802 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
ui-review
Review UI code for StyleSeed design-system compliance, accessibility, mobile ergonomics, spacing discipline, and implementation quality.
react-modern
Use this skill when writing or reviewing React 19+ code in WrongStack. Triggers: user mentions "React", "component", "useState", "useEffect", "Server Component", "Client Component", "Suspense", "useTransition", "use hook".
theme-system
CSS custom properties theme architecture for 4 themes (studio, earth, athlete, gradient) with data-theme attribute switching and theme-aware components. Use when implementing theme switching, defining color schemes, or creating theme-responsive UI elements.
component-architecture
Reusable component patterns for cards, sections, forms, and layouts with consistent prop interfaces and composition strategies. Use when creating new components, refactoring existing ones, or establishing component design patterns.
accessibility-a11y
Semantic HTML, keyboard navigation, focus states, ARIA labels, skip links, and WCAG contrast requirements. Use when ensuring accessibility compliance, implementing keyboard navigation, or adding screen reader support.
responsive-mobile-first
Mobile-first responsive patterns with sticky headers, floating CTAs, accessible navigation, and touch-friendly interactions. Use when implementing responsive layouts, mobile navigation, or ensuring touch-friendly UI.