design-system

A plugin that reads a Storybook design system, a catalog where UI components are documented and previewed. It extracts component markup, styling, themes, and related metadata for use in AI-assisted development.

In plain words
What is it for?
Use it to inspect Storybook components and retrieve their HTML, styles, themes, and metadata when building or updating user interfaces.
Why use it?
Recreating an existing interface component by component can introduce visual and behavioral differences. This gives an agent the source details from the design system to work from.

Plugin for Claude Code

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.

Claude Code
/plugin marketplace add freema/mcp-design-system-extractor
agentmods
npx agentmods add plugins/freema/mcp-design-system-extractor/design-system
Clone the repo
git clone --depth 1 https://github.com/freema/mcp-design-system-extractor

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured The manifest loads nothing itself; its 1 skill, 3 commands, 1 agent, 1 MCP server cost 101 tokens a session between them.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
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 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.

plugins/claude/design-system/.claude-plugin/plugin.json · 12 lines

What it actually says

{
  "name": "design-system",
  "description": "Extract components from Storybook design systems. Get HTML, styles, themes, and component metadata for AI-assisted UI development.",
  "version": "1.1.1",
  "author": {
    "name": "Tomáš Grasl",
    "url": "https://www.tomasgrasl.cz/"
  },
  "repository": "https://github.com/freema/mcp-design-system-extractor",
  "license": "MIT"
}
Contents

What it installs

The manifest is a name and a version. 1 skill, 3 commands, 1 agent, 1 MCP server travel with it, and installing the plugin installs all of them — 101 tokens a session between them. Each is measured on its own page, and each can be installed alone.

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. 3d ago First seen · 12 lines scan A c63cfc42da5b

Subscribe to this mod's changes

design-system is a plugin published in the GitHub repository freema/mcp-design-system-extractor (69 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-30.