adobe/spectrum-design-data is a monorepo containing the design tokens, component schemas, specifications, and related datasets that define Adobe's Spectrum design system; a monorepo keeps these related packages in one repository. It is for Adobe Spectrum SDK and tooling developers who need canonical design-system data and validation artifacts. The catalogue add-ons provide workflows and integrations for working with this design data.
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.
npx skills add adobe/spectrum-design-data --skill design-datagit clone --depth 1 https://github.com/adobe/spectrum-design-dataWrote 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/skills/adobe/spectrum-design-data/design-data)<a href="https://agentmods.dev/skills/adobe/spectrum-design-data/design-data"><img src="https://agentmods.dev/badge/skills/adobe/spectrum-design-data/design-data/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.
<a href="https://agentmods.dev/skills/adobe/spectrum-design-data/design-data"><img src="https://agentmods.dev/badge/skills/adobe/spectrum-design-data/design-data.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00064 | $0.01867 |
| Opus 5.5 | $0.00026 | $0.00747 |
| Sonnet 5.5 | $0.00013 | $0.00373 |
| Haiku 4.5 | $0.00006 | $0.00187 |
Grade A, and why
design-data-agent 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
design-data agent skill
@adobe/design-data-agent-mcp provides in-process wasm tools for validating, querying,
resolving, diffing, and authoring spec-conformant tokens and components from any dataset
on the local filesystem.
Set two path variables once and reference them throughout:
export DESIGN_DATA_PATH=./packages/design-data/tokens
export DESIGN_DATA_SPEC_PATH=./packages/design-data
For Spectrum tokens with zero setup (embedded snapshot), use the design-data skill instead — this skill targets custom or repo-local datasets.
Bootstrap
Add @adobe/design-data-agent-mcp to your .cursor/mcp.json:
{
"mcpServers": {
"design-data-agent": {
"command": "npx",
"args": ["-y", "@adobe/design-data-agent-mcp@latest"],
"env": {
"DESIGN_DATA_PATH": "./packages/tokens/src",
"DESIGN_DATA_COMPONENTS": "./packages/design-data/components",
"DESIGN_DATA_FIELDS": "./packages/design-data/fields"
}
}
}
}
Adjust paths to match your dataset layout. Pin @latest — the embedded Spectrum snapshot is
baked into the wasm at build time and travels with the package version, so there's no separate
data update to run, but plain npx -y <pkg> (no tag) can reuse a cached older build.
Session start — call primer first
Call primer at the start of every session that touches design data. It returns the active
dimensions, component list, taxonomy fields, and token count — structural context that scopes
all subsequent lookups. No inputs required.
Token lookup
Resolve a token to its literal value — resolve_token
Required: property (string) — the bare name.property segment, e.g. "background-color"
or "corner-radius" (see primer().properties for the full list). Not a flattened
legacyKey like "accent-background-color-default" — that form never resolves.
Optional context: colorScheme ("light" or "dark"), scale ("desktop" or "mobile"),
contrast ("regular" or "high"). Optional narrowing: component, variant, state, and
colorRole. Set excludeDeprecated to omit tokens with lifecycle.deprecatedIn.
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.
- today Changed 2eac12934461
- 3d ago Changed 6da92e67ad64
- 6d ago Changed 751fcd0b37ee
- 17d ago Changed c6bbe3d8af0e
- 18d ago Changed 6f7b5896b592
- 24d ago Changed · +21 lines 1e4a4ff7251b
- 26d ago Changed 23376d7a80a1
- 28d ago Changed d8c9be5501d2
- 1mo ago Changed 23f451e1c5ce
- 1mo ago First seen · 174 lines · 64 tokens per session scan A b7ae90be57b1
design-data-agent is a skill published in the GitHub repository adobe/spectrum-design-data (156 stars, last pushed today), licensed Apache-2.0. It adds 64 tokens to every session and 1,867 once invoked, about $0.0003 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-09-03.
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…
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
ss-learn
Capture a human-approved UI design lesson as a privacy-minimized local StyleSeed candidate, review it, and prepare an opt-in share package without transmitting project code, prompts, screenshots, or brand data. Use when a person asks StyleSeed to remember, learn from, generalize, review, or prepare a reusable rule…
omd-apply
A skill that applies a project's DESIGN.md file as visual and brand guidance for interface work. It covers components, colors, fonts, layout, copy, motion, and visual assets.
design-dna
Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects, etc.). Use this skill when: (1) a user wants to see the full 3-dimension design structure/schema, (2) a user provides…
theme-audit
Audit theme parity: tokens missing or unchanged per theme, component tokens bypassing semantics, contrast within each theme, resolver contexts, theme-switch regressions. Triggers: dark mode audit, theme coverage, brand variant parity. For general token structure use token-audit.