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/explore-options)<a href="https://agentmods.dev/commands/owl-listener/designer-skills/explore-options"><img src="https://agentmods.dev/badge/commands/owl-listener/designer-skills/explore-options.svg" alt="Measured on agentmods" 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.00032 | $0.00436 |
| Opus 5 | $0.00016 | $0.00218 |
| Sonnet 5 | $0.00006 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
explore-options 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 3d 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
/explore-options
Run a parallel exploration end to end — frame the decision, build a spread of behaviourally distinct concepts, pressure-test each, and converge with a decision record.
Steps
- Frame the decision — State what this exploration has to settle and fix the criteria that will decide it, before any concept exists, using
concept-selectionskill. - Set the spread — Decide how many concepts the stakes justify and which behavioural dimension they must differ on, using
parallel-conceptsskill. - Draft each concept — Specify structure, content priority, and annotations for every concept at matched fidelity, using
wireframe-specskill. - Trace the difference — Map each concept's user path and confirm the paths actually diverge; collapse any two that do not, using
user-flow-diagramskill. - Pressure-test — Evaluate every concept against usability heuristics on its own terms before any comparison, using
heuristic-evaluationskill. - Converge — Apply the criteria from step 1, choose one concept, and record what each rejected concept was testing and what would bring it back, using
concept-selectionskill.
Output
A concept set and a decision record. The set contains each concept at matched fidelity with its wireframe spec, user flow, and heuristic findings. The record states the criteria fixed in step 1, the chosen concept and what it gives up, and one entry per rejected concept covering what it tested, what it lost on, and its revival condition. The designer takes the chosen concept into detailed design and keeps the record as the answer to "why not the other way".
Consider following up with /test-plan to validate the chosen concept with users before committing to build.
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.
- 3d ago First seen · 17 lines · 32 tokens per session scan A 3b6988aa4cad
explore-options is a command published in the GitHub repository Owl-Listener/designer-skills (2,572 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 436 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-09-05.
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.
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.
design_review
Audit an existing website / app / landing page against SaglitzDesign checklists, the deterministic auditors, and the 0–40 critique rubric.