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 hoangatg/ai-agent-toolkit --skill design-system-buildergit clone --depth 1 https://github.com/hoangatg/ai-agent-toolkitWrote 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/hoangatg/ai-agent-toolkit/design-system-builder)<a href="https://agentmods.dev/skills/hoangatg/ai-agent-toolkit/design-system-builder"><img src="https://agentmods.dev/badge/skills/hoangatg/ai-agent-toolkit/design-system-builder.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.00030 | $0.00810 |
| Opus 5 | $0.00015 | $0.00405 |
| Sonnet 5 | $0.00006 | $0.00162 |
| Haiku 4.5 | $0.00003 | $0.00081 |
Grade A, and why
design-system-builder 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 4d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design System Builder
Design once, use everywhere. Consistency at scale.
1. Core Components
Design System Layers
| Layer | Contains |
|---|---|
| Tokens | Colors, spacing, typography, shadows |
| Foundations | Grid, layout, breakpoints |
| Components | Buttons, inputs, cards, modals |
| Patterns | Forms, navigation, data display |
| Templates | Full page layouts |
2. Design Tokens
Token Architecture
| Level | Example | Purpose |
|---|---|---|
| Global | color-blue-500 |
Platform values |
| Alias | color-primary |
Semantic mapping |
| Component | button-bg-primary |
Component-specific |
Token Formats
| Tool | Format |
|---|---|
| Style Dictionary | JSON → CSS/JS/iOS/Android |
| Figma Tokens | Figma plugin → JSON |
| CSS Custom Properties | Native browser support |
3. Component Design
Component API Principles
| Principle | Application |
|---|---|
| Composition | Compound components over mega-props |
| Polymorphic | as prop for element type |
| Accessible | ARIA attributes built-in |
| Themed | Tokens, not hardcoded values |
| Documented | Props table + examples + guidelines |
Component Maturity Levels
| Level | Requirements |
|---|---|
| Alpha | Functional, basic tests |
| Beta | Accessible, documented, stable API |
| Stable | Full tests, Storybook, design approved |
| Deprecated | Migration guide, timeline |
4. Documentation
Docs Site Requirements
| Section | Content |
|---|---|
| Getting Started | Install, setup, quickstart |
| Foundations | Colors, typography, spacing |
| Components | Live examples, props, guidelines |
| Patterns | Common usage patterns |
| Changelog | Version history |
Tools
| Tool | Purpose |
|---|---|
| Storybook | Component playground + docs |
| Chromatic | Visual regression testing |
| Docusaurus | Documentation site |
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.
- 4d ago First seen · 127 lines · 30 tokens per session scan A ab7f24be8a2a
design-system-builder is a skill published in the GitHub repository hoangatg/ai-agent-toolkit (1 stars, last pushed 5mo ago), licensed MIT. It adds 30 tokens to every session and 810 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-03.
Other skills, from other repositories
ux-ui
Use this agent when you need to design, audit, migrate, rewire, or rewrite UX/UI.
accessibility
You are the Accessibility (a11y) Specialist, ensuring applications are accessible to all users, including those with disabilities. You enforce WCAG standards and inclusive design principles.
a11y
Use this agent for WCAG 2.1 accessibility audits, screen reader testing, keyboard navigation, color contrast, ARIA validation, and inclusive design reviews.
codex
Delegate coding tasks to the OpenAI Codex CLI for features, refactoring, PR reviews, and batch fixes. Requires the codex CLI and typically a git repository.
opencode
Delegate coding tasks to the OpenCode CLI for feature work, refactoring, PR review, and autonomous-style runs. Requires opencode installed where the agent can execute shell commands.
refactoring-ui
Apply UI design principles from Refactoring UI by Adam Wathan & Steve Schoger. Covers visual hierarchy (size, weight, color, spacing), layout systems (spacing scales, grids), typography (type scales, line-height, alignment), color (HSL palettes, shade systems, accessible contrast), depth (shadow elevation, overlap)…