agentmods.dev

design-system

design-system is a command for Claude Code from CrashBytes/claude-role-skills. It costs 7 tokens per session (437 once invoked), scanned A, original, Apache-2.0.

A tool for creating or reviewing a component design system, the shared visual rules and reusable interface parts used across a product. It can define colors, spacing, typography, shadows, borders, breakpoints, component conventions, and starter components.

In plain words
What is it for?
Use it to start a design system, define shared visual tokens and component APIs, create starter buttons, inputs, and cards, or audit an existing interface codebase for inconsistencies.
Why use it?
It helps keep interfaces consistent as a codebase grows. Reviewing an existing system can expose duplicate colors, uneven spacing, and inconsistent naming or component patterns.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the role-based-skills plugin — 7 skills, 15 commands shipped together

not rated 8repo 8mo ago A scan 7 tokens original Apache-2.0

Good fit Use it to start a design system, define shared visual tokens and component APIs, create starter buttons, inputs, and cards, or audit an existing interface codebase for inconsistencies.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/crashbytes/claude-role-skills/design-system
View source ↗ CrashBytes/claude-role-skills
Install

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.

Clone the repo
git clone --depth 1 https://github.com/CrashBytes/claude-role-skills

Made for: Claude Code.

Or install role-based-skills, the plugin that ships this one along with the rest of its 7 skills, 15 commands.

Wrote 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.

agentmods badge for design-system

README.md
[![agentmods](https://agentmods.dev/badge/commands/crashbytes/claude-role-skills/design-system/github.svg)](https://agentmods.dev/commands/crashbytes/claude-role-skills/design-system)
Your own site
<a href="https://agentmods.dev/commands/crashbytes/claude-role-skills/design-system"><img src="https://agentmods.dev/badge/commands/crashbytes/claude-role-skills/design-system/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.

agentmods 80×15 button for design-system

Your own site · 80×15
<a href="https://agentmods.dev/commands/crashbytes/claude-role-skills/design-system"><img src="https://agentmods.dev/badge/commands/crashbytes/claude-role-skills/design-system.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 437 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00007 $0.00437
Opus 5.5 $0.00003 $0.00175
Sonnet 5.5 $0.00001 $0.00087
Haiku 4.5 $0.00001 $0.00044

Measured 2mo ago against content hash 42f7e74116b5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 2mo 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.

commands/design-system.md · 49 lines

What it actually says

Design System

Design, initialize, or audit a component design system.

Arguments

Action: $ARGUMENTS

Workflow

If action is init (or no existing system detected):

  1. Scaffold design tokens

    • Colors: primary, secondary, neutral (8-10 shades), semantic (success, warning, error, info)
    • Spacing: 4px base unit scale (4, 8, 12, 16, 24, 32, 48, 64)
    • Typography: font families, modular scale (1.25 ratio), line heights
    • Shadows: elevation levels (sm, md, lg, xl)
    • Borders: radii, widths
    • Breakpoints: sm (640px), md (768px), lg (1024px), xl (1280px)

  2. Define component API conventions

    • Standard props: size, variant, disabled, className
    • Composition pattern: composable children over complex prop objects
    • Ref forwarding pattern
    • Polymorphic as prop pattern

  3. Generate starter components

    • Button (primary, secondary, outline, ghost, destructive)
    • Input (text, email, password, with label and error state)
    • Card (header, body, footer composition)

If action is audit:

  1. Scan the codebase for existing components, tokens, and patterns
  2. Identify inconsistencies: duplicate colors, inconsistent spacing, mixed naming conventions
  3. Report: what exists, what's missing, what needs consolidation

If action is add-component <name>:

  1. Generate the component following existing design system patterns
  2. Include: component file, types, accessible markup, keyboard handling
  3. Follow existing naming and prop conventions detected in the codebase
Changes

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.

  1. 2mo ago First seen · 49 lines · 7 tokens per session scan A 42f7e74116b5

Subscribe to this mod's changes

design-system is a command published in the GitHub repository CrashBytes/claude-role-skills (8 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 7 tokens to every session and 437 once invoked, about $0.0000 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-31.

Claude CodeDesign and UXagent-skillsclaude-pluginclaude-skillsinfosec
Related

design-system compared with commands from other repositories

design-system next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
design-systemCrashBytes/claude-role-skillsCommand88mo agoApache-2.0A7Claude Code
customizesystemoperators/claude-pluginsCommand6todayMITA9Claude Code
color-palettejezweb/claude-skillsCommand1.1k1mo agoMITA9Claude Code
ux-extractjezweb/claude-skillsCommand1.1k1mo agoMITB16Claude Code
summaryclownware/product-devCommand323d agoApache-2.0A27Claude Code
ledger-commitnunoamorim99/agile-ledgerCommand120d agoMITA18Claude Code
bugnunoamorim99/agile-ledgerCommand120d agoMITA19Claude Code