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.
git 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/commands/owl-listener/designer-skills/critique-ux)<a href="https://agentmods.dev/commands/owl-listener/designer-skills/critique-ux"><img src="https://agentmods.dev/badge/commands/owl-listener/designer-skills/critique-ux/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/commands/owl-listener/designer-skills/critique-ux"><img src="https://agentmods.dev/badge/commands/owl-listener/designer-skills/critique-ux.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.00026 | $0.00366 |
| Opus 5 | $0.00013 | $0.00183 |
| Sonnet 5 | $0.00005 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
critique-ux 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 8d 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.
What it actually says
/critique-ux
Run a focused functional critique on a screen. This command covers the three dimensions most likely to block task completion: whether actions are discoverable, whether the right information is present, and whether priority is clear. Use this for quick feedback loops, PM-led reviews, or when you want functional critique without a full visual audit.
Steps
- Visual hierarchy — Identify entry point and whether the primary action reads clearly using
critique-visual-hierarchyskill. - Affordance — Evaluate clickability signals, state visibility, CTA clarity, and action discoverability using
critique-affordanceskill. - Information density — Assess cognitive load, content priority, scanning patterns, and progressive disclosure using
critique-information-densityskill. - Prioritise — Collect every flagged issue and rank them:
- P1 — Critical: Blocks task completion or hides a required action; fix before shipping.
- P2 — Important: Slows the user or creates confusion; fix in current sprint.
- P3 — Polish: Minor friction or clarity improvement; address when capacity allows.
Output
A prioritised fix list grouped by level. Each item includes:
- Issue: what is wrong
- Dimension: Hierarchy / Affordance / Density
- Fix: the specific change required Conclude with one sentence summarising the biggest functional risk on the screen.
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.
- 8d ago First seen · 21 lines · 26 tokens per session scan A f6d32c14a7c0
critique-ux is a command published in the GitHub repository Owl-Listener/designer-skills (2,609 stars, last pushed 6d ago), licensed MIT. It adds 26 tokens to every session and 366 once invoked, about $0.0001 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 commands, from other repositories
hatch3r-design-system-create
Create a project design system from brand assets or an elicitation dialog — DTCG 2025.10 token emission, 3-tier taxonomy (primitive → semantic → component), OKLCH ramps, dual output design.md + design-tokens.json, gated on WCAG 2.2 AA contrast, 100% theme parity, and 0 dangling aliases.
design
Command dispatcher for design.
build_dashboard
Design & build a dense SaaS dashboard or app shell — navigation, tables, empty/loading states, a generated product-UI system — not a marketing page in disguise.
port_to_platform
Take an existing design or implementation to another platform (iOS ↔ Android ↔ macOS ↔ web) — porting the intent and IA, not the components.
redesign
Improve an existing UI (bolder, quieter, cleaner, higher-converting) using SaglitzDesign craft standards, with measured before→after.
critique_screenshot
Grounded, reproducible visual critique of an attached UI screenshot against the fixed 0–40 rubric — cites specific elements, no padding.