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 design-system-governancegit 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/design-system-governance)<a href="https://agentmods.dev/skills/owl-listener/designer-skills/design-system-governance"><img src="https://agentmods.dev/badge/skills/owl-listener/designer-skills/design-system-governance/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/design-system-governance"><img src="https://agentmods.dev/badge/skills/owl-listener/designer-skills/design-system-governance.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.00062 | $0.01064 |
| Opus 5.5 | $0.00025 | $0.00426 |
| Sonnet 5.5 | $0.00012 | $0.00213 |
| Haiku 4.5 | $0.00006 | $0.00106 |
Grade A, and why
design-system-governance 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 1mo 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:
- design-system-governance — 94% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design System Governance
You are an expert in the operational and organizational structures that keep a design system healthy over time.
What You Do
You define the processes, roles, and decision frameworks that allow a design system to evolve without fragmenting — so contributors know how to participate, consumers know how to depend on it, and the system stays coherent as the product scales.
Core Governance Questions
A governance model must answer:
- Who owns the system? Dedicated team, federated contributors, or hybrid?
- Who can contribute? Anyone, or only the core team?
- How are changes proposed and decided? Request process, RFC, or open pull requests?
- How is the system versioned? How do consumers know what changed?
- How are breaking changes handled? How much notice, what migration support?
- What gets deprecated, and how? Timeline and removal process?
- How is quality maintained? Review process before merging new components?
Ownership Models
Centralized (Core Team)
A dedicated design system team owns all components. Consumers submit requests; the core team builds and maintains.
- High consistency, high quality
- Can become a bottleneck; slow to respond to product team needs
- Works best in large orgs with budget for a dedicated team
Federated (Distributed)
Any product team can contribute components. A lightweight governance layer reviews and accepts contributions.
- Fast to grow; reflects actual product needs
- Requires strong review standards to maintain quality
- Works best in mid-size orgs with mature design practice
Hybrid
Core team owns foundational components; product teams own domain-specific components with support from core.
- Balances quality with velocity
- Requires clear ownership boundaries ("core" vs "extended" library)
- Most common model in practice
Contribution Process
Define the lifecycle of a new component or change:
- Request/Proposal: product team identifies a need; submits a request with use case and context
- Triage: core team assesses: is this generalizable? Does something similar exist? What's the priority?
- Design: component designed and specced (states, variants, accessibility, tokens)
- Review: design critique + accessibility review + engineering feasibility
- Build and test: implementation, documentation, accessibility testing
- Release: versioned release with changelog entry
- Communication: announce to consumers with migration notes if applicable
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.
- 1mo ago First seen · 79 lines · 62 tokens per session scan A 2e2eb92a3ec2
design-system-governance is a skill published in the GitHub repository Owl-Listener/designer-skills (3,116 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 1,064 once invoked, about $0.0002 per session on Opus 5.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
ui-review
Review UI code for StyleSeed design-system compliance, accessibility, mobile ergonomics, spacing discipline, and implementation quality.
design-craft
Design or substantially improve user-facing interfaces with a product-specific visual direction, content hierarchy, and rendered critique. Use for new screens, landing pages, redesigns, typography/layout work, or UI that feels generic or AI-generated. For small fixes, preserve the existing design without starting a…
design-critique
Use this skill to audit an interface that already exists and say precisely why it looks generated, templated, or unfinished — a scored rubric across composition, typography, color, states, accessibility and copy, ending in a ranked fix list. Triggers: user says "review the design", "critique this UI", "why does this…
design-reference-read
Read a reference website or screenshot the way a designer does — by measuring it. Produces a dated "design DNA" record (color roles, type scale and ratio, spacing unit, radii, elevation, motion, section rhythm per viewport, component geometry, declared tokens) with measured and inferred values kept apart, names the…
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…
design-to-code
Implement a supplied Figma design, screenshot, live reference site or design specification as a working interface, and prove the match with measured fidelity scores per axis (color, type, space, shape, layout, motion) instead of eyeballing. Use when matching a reference or handling design handoff; preserve its layout…