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 agentmods add commands/owl-listener/designer-skills/create-componentgit 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/create-component)<a href="https://agentmods.dev/commands/owl-listener/designer-skills/create-component"><img src="https://agentmods.dev/badge/commands/owl-listener/designer-skills/create-component.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.00021 | $0.00221 |
| Opus 5 | $0.00010 | $0.00111 |
| Sonnet 5 | $0.00004 | $0.00044 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
create-component 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:
- create-component — 94% identical, 2 lines differ
What it actually says
/create-component
Generate a comprehensive component specification.
Steps
- Research — Understand purpose and common implementations.
- Anatomy — Break down parts using
component-specskill. - Variants — Define size, style, layout variants.
- States — Map interactive states using
component-specskill. - Tokens — Identify consumed tokens using
design-tokenskill. - Accessibility — Specify ARIA, keyboard, screen reader using
accessibility-auditskill. - Naming — Follow conventions using
naming-conventionskill. - Documentation — Structure using
documentation-templateskill.
Output
Complete spec: overview, anatomy, props/API, variants, states, accessibility, usage guidelines, tokens.
Consider following up with /audit-system.
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 · 19 lines · 21 tokens per session scan A 4802709f2c93
create-component is a command published in the GitHub repository Owl-Listener/designer-skills (2,502 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 221 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-08-30.
Other commands, from other repositories
dashboard-session-fork
Fork a session into a new one. Usage /dashboard:session-fork.
dashboard-session-hide
Hide a session from the dashboard list. Usage /dashboard:session-hide.
dashboard-session-unhide
Unhide a previously hidden session. Usage /dashboard:session-unhide.
eg-fix-bug
Fix a bug using the elephant/goldfish workflow — problem doc, goldfish diagnosis check, failing test, fix, review, validate.
clone
Runtime entry point for reverse-engineering an external website reference into a clean, code-native prototype design system.
retrofit
Runtime entry point for unifying a drifted prototype under one design system.