metadata-schema-generator

metadata-schema-generator is a skill for Claude Code from murphytrueman/design-system-ops. It costs 139 tokens per session (3,322 once invoked), scanned A, original, MIT.

A tool for creating JSON files that describe design-system components in a form software can read. The files can record component options, behavior, allowed combinations, accessibility requirements, and business context.

In plain words
What is it for?
Use it to define machine-readable rules for buttons, forms, and other interface components, including their options, behavior, composition limits, and accessibility contracts.
Why use it?
It turns details that are often written only for people into explicit data that coding, testing, and other software tools can use without interpreting prose.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the design-system-ops plugin — 40 skills, 14 commands shipped together

Good fit Use it to define machine-readable rules for buttons, forms, and other interface components, including their options, behavior, composition limits, and accessibility contracts.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/murphytrueman/design-system-ops/metadata-schema-generator
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 murphytrueman/design-system-ops --skill metadata-schema-generator
Clone the repo
git clone --depth 1 https://github.com/murphytrueman/design-system-ops

Made for: Claude Code.

Or install design-system-ops, the plugin that ships this one along with the rest of its 40 skills, 14 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 metadata-schema-generator

README.md
[![agentmods](https://agentmods.dev/badge/skills/murphytrueman/design-system-ops/metadata-schema-generator.svg)](https://agentmods.dev/skills/murphytrueman/design-system-ops/metadata-schema-generator)
Your own site
<a href="https://agentmods.dev/skills/murphytrueman/design-system-ops/metadata-schema-generator"><img src="https://agentmods.dev/badge/skills/murphytrueman/design-system-ops/metadata-schema-generator.svg" alt="Measured on agentmods" height="20"></a>
Per session 139 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,322 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.00139 $0.03322
Opus 5 $0.00069 $0.01661
Sonnet 5 $0.00028 $0.00664
Haiku 4.5 $0.00014 $0.00332

Measured 8d ago against content hash 9dac717d3676, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

metadata-schema-generator 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 8d 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.

skills/metadata-schema-generator/SKILL.md · 381 lines

How it starts

The opening of the file, as written. The whole thing — 381 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Metadata schema generator

A skill for generating structured JSON metadata schemas for design system components. These schemas encode everything an AI agent, MCP server, code generator, or testing framework needs to work with a component programmatically — props, behavioural rules, composition constraints, accessibility contracts, and business context — in a format that does not require natural language parsing.

Context

Component documentation serves humans. Component metadata serves machines. The distinction matters because the information needs are different, the format requirements are different, and the failure modes are different.

A human reading a component's documentation can infer that "this button triggers the primary action" means it should be visually prominent and placed in the expected location. A code generation agent reading that same string cannot infer any of that — it needs explicit data: { "role": "primary_action", "visual_weight": "high", "placement": ["form_footer", "dialog_footer", "page_header"] }.

Most design systems have one layer of machine-readable data: TypeScript interfaces or PropTypes declarations that define prop names and types. This is necessary but insufficient. A TypeScript interface tells a tool that a Button accepts a variant prop of type "primary" | "secondary" | "ghost" — but it does not tell the tool when to use primary vs secondary, which combinations of props are prohibited, where the component can be placed in a layout, or what accessibility contract it must honour.

Structured metadata fills this gap. It encodes the knowledge layer between "what the component accepts" (TypeScript) and "how the component should be used" (documentation) as machine-readable data that tooling consumes directly.

The ai-component-description skill produces text descriptions optimised for LLM consumption. This skill produces structured data optimised for programmatic consumption. Together they serve the two modes of AI interaction: conversational (descriptions) and deterministic (metadata).

Read the full file on GitHub · 381 lines

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. 8d ago First seen · 381 lines · 139 tokens per session scan A 9dac717d3676

Subscribe to this mod's changes

metadata-schema-generator is a skill published in the GitHub repository murphytrueman/design-system-ops (176 stars, last pushed 16d ago), licensed MIT. It adds 139 tokens to every session and 3,322 once invoked, about $0.0007 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-08-30.

Related

Other skills, from other repositories

extract-design

Extract the full design language from any website URL. Produces 8 output files including AI-optimized markdown, visual HTML preview, Tailwind config, React theme, shadcn/ui theme, Figma variables, W3C design tokens, and CSS variables. Also runs WCAG accessibility scoring. Use when user says 'extract design', 'get…

Manavarya09/design-extract · 98 tokens

designlang-tokens

Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.

Manavarya09/design-extract · 30 tokens

roast-my-design-system

Roast the current repo's design system with real data. Runs a deterministic scanner (no tokens, 1s) that counts everything that betrays a design system, from colours and their near-identical twins to greys, spacing values, typefaces, duplicated and never-imported components, inline styles, !important and arbitrary…

gregkozakiewicz/roast-my-design-system · 161 tokens

design-engineering

Premium design engineering skill for agentic workflows — produces high-end, distinctive UI designs using DESIGN.md as the portable contract across Pencil MCP (in-IDE canvas), Figma MCP (team handoff + design tokens), and Google Stitch (vibe exploration + AI generation). Enforces anti-generic principles, WCAG 2.2 AA…

broomva/skills · 231 tokens

sheleg-design

A design skill for planning how websites, dashboards, mobile screens, and agent interfaces look and move, including cinematic pages with layered motion.

ssheleg/sheleg-design-skill · 292 tokens

generate-figma-screen

Kod veya açıklamadan Figma'da tam ekran/sayfa oluşturur. Yayınlanmış design system bileşenlerini arayıp instance olarak yerleştirir; hardcode değer yerine DS token'larını kullanır. "Figma'da ekran oluştur", "kodu Figma'ya çevir", "landing page çiz", "ekran tasarla", "generate screen", "UI'ı Figma'ya aktar"…

atezer/FMCP · 118 tokens