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.
git clone --depth 1 https://github.com/christopherlouet/claude-baseWrote 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/christopherlouet/claude-base/dev-design-system)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/dev-design-system"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/dev-design-system.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.00000 | $0.00314 |
| Opus 5 | $0.00000 | $0.00157 |
| Sonnet 5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
dev-design-system 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 3d 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.
What it actually says
Agent DEV-DESIGN-SYSTEM
Creation and maintenance of design systems and component libraries.
Request context
$ARGUMENTS
Objective
Create or audit a complete design system with tokens, primitive components, composite components and patterns, all documented in Storybook.
Workflow
- Define design tokens (semantic colors, typography, spacing, shadows, animations)
- Generate tokens with Style Dictionary (CSS variables, TypeScript, Tailwind)
- Create primitive components (Button, Input, Text, Icon, Badge) with variants (cva)
- Create composite components (Form, Modal, Dropdown, Table, Navigation)
- Define patterns (Auth Flow, Settings, Dashboard, Empty States)
- Implement theming (ThemeProvider, light/dark/system)
- Document each component in Storybook with stories and argTypes
- Ensure WCAG 2.1 AA accessibility on each component
Expected output
Audit of the existing design system or creation plan by phases (tokens > primitives > composites > documentation).
Related agents
| Agent | Usage |
|---|---|
/dev:dev-component |
Create components |
/qa:wcag-audit |
Accessibility |
/doc:doc-generate |
Documentation |
IMPORTANT: Tokens are the source of truth - never hardcoded values.
IMPORTANT: Each component must be accessible (WCAG 2.1 AA).
YOU MUST document each component in Storybook.
NEVER duplicate styles - use tokens.
Think hard about the consistency and reusability of the 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.
- 3d ago First seen · 48 lines · 0 tokens per session scan A f8829faed5dc
dev-design-system is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 314 tokens. 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 commands, from other repositories
perf-audit
Performance audit for web applications.
scaffold
Scaffold project components from templates.
bliss
Create distinctive, human-centered frontend interfaces. Use for UI components, pages, and applications with bold aesthetics and WCAG compliance.
ui-phase
Generate UI-SPEC.md design contracts for frontend-heavy phases.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.