component-design-systems

component-design-systems is a skill for Claude Code, Codex from cosmicstack-labs/mercury-agent-skills. It costs 22 tokens per session (413 once invoked), scanned A, original, MIT.

A guide to building shared libraries of reusable interface components, with consistent design tokens, accessibility, documentation, and component APIs.

In plain words
What is it for?
Creating buttons, inputs, forms, tables, and other reusable components; defining shared styles; and documenting how teams use them.
Why use it?
It helps teams avoid repeating UI work and prevents inconsistent or inaccessible interfaces across products.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Creating buttons, inputs, forms, tables, and other reusable components; defining shared styles; and documenting how teams use them.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cosmicstack-labs/mercury-agent-skills/component-design-systems
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.

Any agent
npx skills add cosmicstack-labs/mercury-agent-skills --skill component-design-systems
Clone the repo
git clone --depth 1 https://github.com/cosmicstack-labs/mercury-agent-skills

Made for: Claude Code, Codex.

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 component-design-systems

README.md
[![agentmods](https://agentmods.dev/badge/skills/cosmicstack-labs/mercury-agent-skills/component-design-systems/github.svg)](https://agentmods.dev/skills/cosmicstack-labs/mercury-agent-skills/component-design-systems)
Your own site
<a href="https://agentmods.dev/skills/cosmicstack-labs/mercury-agent-skills/component-design-systems"><img src="https://agentmods.dev/badge/skills/cosmicstack-labs/mercury-agent-skills/component-design-systems/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 component-design-systems

Your own site · 80×15
<a href="https://agentmods.dev/skills/cosmicstack-labs/mercury-agent-skills/component-design-systems"><img src="https://agentmods.dev/badge/skills/cosmicstack-labs/mercury-agent-skills/component-design-systems.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 413 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00022 $0.00413
Opus 5 $0.00011 $0.00206
Sonnet 5 $0.00004 $0.00083
Haiku 4.5 $0.00002 $0.00041

Measured 5d ago against content hash 393e19c52806, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

component-design-systems 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 5d 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.

categories/frontend/component-design-systems/SKILL.md · 60 lines

What it actually says

Component Design Systems

Patterns for building scalable, accessible, and maintainable component libraries.

Architecture

design-system/
├── tokens/              # Design tokens
│   ├── colors.json
│   ├── typography.json
│   └── spacing.json
├── primitives/          # Base components
│   ├── Button/
│   ├── Input/
│   └── Text/
├── patterns/            # Composed patterns
│   ├── FormField/
│   ├── DataTable/
│   └── Modal/
└── docs/               # Documentation
    └── Storybook/

Component API Design

// Compound component pattern
<Select>
  <Select.Label>Country</Select.Label>
  <Select.Trigger>
    <Select.Value placeholder="Select a country" />
  </Select.Trigger>
  <Select.Content>
    <Select.Item value="us">United States</Select.Item>
    <Select.Item value="uk">United Kingdom</Select.Item>
  </Select.Content>
</Select>

Common Mistakes

  1. No design tokens: Hardcoded values everywhere. Use tokens for colors, spacing, typography.
  2. Missing accessibility: Always include ARIA labels, keyboard nav, focus management.
  3. Too opinionated: Components should work out-of-box but be customizable via props/composition.
  4. No versioning strategy: Use semver. Document breaking changes clearly.
  5. No visual regression tests: Use Chromatic/Percy to catch unintended style changes.
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. 5d ago First seen · 60 lines · 22 tokens per session scan A 393e19c52806

Subscribe to this mod's changes

component-design-systems is a skill published in the GitHub repository cosmicstack-labs/mercury-agent-skills (471 stars, last pushed 14d ago), licensed MIT. It adds 22 tokens to every session and 413 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

frontend-ui-engineering

Builds production-quality, accessible, responsive user-facing UIs. Use when building or modifying interfaces and pages, creating components, implementing layouts, meeting WCAG accessibility requirements, managing state, or when the output needs to look and feel production-quality rather than AI-generated.

addyosmani/agent-skills · 58 tokens

playground

Creates interactive HTML playgrounds — self-contained single-file explorers that let users configure something visually through controls, see a live preview, and copy out a prompt. Use when the user asks to make a playground, explorer, or interactive tool for a topic.

anthropics/claude-plugins-official · 53 tokens

frontend-design

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

anthropics/claude-plugins-official · 40 tokens

baseline-ui

Quickly deslop UI code by fixing spacing, hierarchy, typography, and small layout issues. Use when the interface needs a fast cleanup or polish pass.

ibelick/ui-skills · 34 tokens

web-design-engineer

Build or redesign polished browser-rendered visual artifacts with HTML/CSS/JavaScript/React: pages, dashboards, prototypes, slide decks, animations, UI mockups, and data visualizations. Use for visual front-end creation, design-system exploration, design critique, or explicit browser acceptance / QA of a web artifact.…

ConardLi/garden-skills · 96 tokens

frontend-design

A guide for building polished web interfaces such as pages, dashboards, applications, posters, and reusable React or Vue components. It covers visual direction, layout, typography, colors, animation, accessibility, and working HTML, CSS, or JavaScript code.

xstongxue/best-skills · 103 tokens