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 aditya-ariosity/ux-ui-skills --skill design-system-reviewgit clone --depth 1 https://github.com/aditya-ariosity/ux-ui-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/aditya-ariosity/ux-ui-skills/design-system-review)<a href="https://agentmods.dev/skills/aditya-ariosity/ux-ui-skills/design-system-review"><img src="https://agentmods.dev/badge/skills/aditya-ariosity/ux-ui-skills/design-system-review/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/aditya-ariosity/ux-ui-skills/design-system-review"><img src="https://agentmods.dev/badge/skills/aditya-ariosity/ux-ui-skills/design-system-review.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.00105 | $0.01203 |
| Opus 5 | $0.00053 | $0.00602 |
| Sonnet 5 | $0.00021 | $0.00241 |
| Haiku 4.5 | $0.00011 | $0.00120 |
Grade A, and why
design-system-review 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 yesterday.
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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design System Review
Review the system as a product and an operating model, not a screenshot library. A healthy system creates shared decisions, accessible defaults, predictable behavior, and a credible path from design to production.
1. Define the system boundary
Establish:
- products, platforms, brands, themes, locales, and teams served;
- available evidence: token files, component code, Storybook, Figma libraries, documentation, usage analytics, product screenshots, issue logs;
- source of truth for tokens, components, content, and release status;
- expected consumers and valid extension points;
- maturity stage: inventory, emerging library, adopted system, or multi-brand platform.
Do not equate visual inconsistency with system failure until intent and ownership are known.
2. Build an evidence inventory
Sample real product usage, not only pristine documentation. Create:
Pattern | Instances | Intended source | Observed variants | State gaps | Accessibility risk | Adoption signal | Owner
Synthetic example: Button | 24 product instances | Shared component | Five colors; three focus treatments | Focus and loading | Missing focus | 17/24 use shared | UI platform
Trace representative components from semantic token to design asset to code to product. Record drift at the layer where it originates.
3. Review four layers
Foundations and tokens
Read references/tokens-and-theming.md. Inspect semantic naming, primitive separation, themes and aliases, accessibility-critical typography and motion, deprecation, and distribution.
Components and patterns
Read references/component-contract.md. Inspect anatomy, variants, states, semantics, keyboard and responsive behavior, API boundaries, escape hatches, and test coverage.
Documentation and tooling
Inspect discoverability, realistic examples, rationale, design-code linkage, migration guidance, release notes, and executable stories or tests.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday Changed · +9 lines · +30 tokens per session a0600bf2c453
- 8d ago First seen · 124 lines · 75 tokens per session scan A 3a5d90c8c228
design-system-review is a skill published in the GitHub repository aditya-ariosity/ux-ui-skills (2 stars, last pushed 2d ago), licensed MIT. It adds 105 tokens to every session and 1,203 once invoked, about $0.0005 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-04.
Other skills, from other repositories
design-with-claude
Use when design work needs a product designer's eye: auditing a codebase for design-system gaps, fixing WCAG contrast and unlabeled inputs, choosing type scales or spacing steps, reviewing UI that looks generic or AI-generated, or designing forms, tables, dashboards, navigation, checkout, onboarding, dark mode, and…
Design
A comprehensive design operating system synthesized from 10 canonical design books. Covers research, typography, color theory, composition, branding, logo design, storytelling, web design, creative process, and professional practice.
Design
A comprehensive design operating system synthesized from 10 canonical design books. Covers research, typography, color theory, composition, branding, logo design, storytelling, web design, creative process, and professional practice.
hps-bauhaus
A visual-design fundamentals course for new brand designers — grid, type, color, and the exercises that build the eye. Built as a decision-grade professional training deck for junior designers, new hires.
html-ppt-zhangzara-pink-script
A wedding-anniversary tribute photo essay — a decade in scenes, the turning points, and the quiet meaning of staying. Built as a decision-grade story deck for couple, family, friends.
html-ppt-zhangzara-blue-professional
OpenDesign's QBR for the executive committee: what moved, what stalled, and the resource reallocation ask. Built as a decision-grade corporate strategy deck for executive committee.