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/designpowers --skill design-discoverygit clone --depth 1 https://github.com/Owl-Listener/designpowersWrote 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/designpowers/design-discovery)<a href="https://agentmods.dev/skills/owl-listener/designpowers/design-discovery"><img src="https://agentmods.dev/badge/skills/owl-listener/designpowers/design-discovery/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/designpowers/design-discovery"><img src="https://agentmods.dev/badge/skills/owl-listener/designpowers/design-discovery.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- 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.00045 | $0.01780 |
| Opus 5 | $0.00023 | $0.00890 |
| Sonnet 5 | $0.00009 | $0.00356 |
| Haiku 4.5 | $0.00005 | $0.00178 |
Grade A, and why
design-discovery 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Discovery
Discovery is where design begins. Before pixels, before wireframes, before any visual decisions — understand the problem. This skill ensures you never design the wrong thing well.
Welcome Gate
BEFORE running discovery, check whether the Designpowers welcome sequence has been shown this session. If the user has not yet seen the welcome (the bird, the greeting, and the walkthrough offer), you MUST invoke the using-designpowers skill FIRST and complete the welcome sequence before returning here. The bird must appear before any work begins. No exceptions.
The Rule
DO NOT proceed to any design, UI, or implementation work until discovery is complete and the user has approved the design brief.
Discovery Modes
Quick Discovery (for POCs and small tasks)
When the user says "proof of concept", "POC", "quick", "small", or the task is clearly exploratory:
- Keep it light. Ask a few essentials in a conversational way — not as a numbered checklist:
"Quick version: what's the problem, who's it for, and what does success feel like? If you've got a design system or any references you love, throw those in too."
- Write the brief immediately from their answers — don't ask follow-up rounds
- Present the brief for approval in one block (not section by section)
- Create
design-state.mdin the project root immediately after brief approval
Quick discovery should take one user message of answers, not three. But the question should still feel like a person asking, not a form.
Full Discovery (for products and complex tasks)
When the task is a full product, involves multiple stakeholders, or the user explicitly wants depth — use the full process below.
Process
Step 1: Understand the Context
Before asking questions, gather what already exists:
- Read any existing design documents, specs, or briefs in the project
- Check for an existing design system, component library, or style guide
- Look at the current state of what the user is working on
- Identify the platform, tech stack, and any constraints
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.
- 9d ago First seen · 165 lines · 45 tokens per session scan A 9c9c3454acfd
design-discovery is a skill published in the GitHub repository Owl-Listener/designpowers (243 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 1,780 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
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.
tailwind-shadcn
Tailwind CSS utility patterns with shadcn/ui component usage, theming via CSS variables, and responsive design. Use when styling components, installing shadcn components, implementing dark mode, or creating consistent design systems.
anti-slop-frontend
A mechanical, countable anti-slop checklist for AI-generated frontend. Catches the specific signatures an undirected model defaults to: AI-purple glows, Inter-everywhere, em-dashes, div-based fake screenshots, eyebrow-on-every-section, beige+brass "premium" palettes, generic Jane Doe / Acme data. Advisory layer that…
frontend-mockup-loop
Plan, build, and iterate UX-friendly frontend mockups via a ground→contract→mockup→test→fix→learn loop, acting as an expert UX designer who grounds every decision in externally documented public design rules (Nielsen heuristics, Laws of UX, WCAG, GOV.UK/USWDS/Material). Uses the bundled servemockup, scoremockup, and…
frontend-mockup-loop-dashboard
Dashboard-specific adapter on the generic frontend-mockup-loop skill: binds the 7-step design loop to pi-agent-dashboard component sources, theme-system tokens, and isolated verification. Use when designing/redesigning any pi-agent-dashboard client surface. Triggers: "design a dashboard screen", "mockup a dashboard…
goga-define-experience
Define the user experience required to achieve the established product goals and solve the identified problem.