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.
git 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/rules/adobe/spectrum-design-data/legacy-tokens)<a href="https://agentmods.dev/rules/adobe/spectrum-design-data/legacy-tokens"><img src="https://agentmods.dev/badge/rules/adobe/spectrum-design-data/legacy-tokens/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/rules/adobe/spectrum-design-data/legacy-tokens"><img src="https://agentmods.dev/badge/rules/adobe/spectrum-design-data/legacy-tokens.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.00346 |
| Opus 5.5 | $0.00000 | $0.00138 |
| Sonnet 5.5 | $0.00000 | $0.00069 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
legacy-tokens 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 yesterday.
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.
What it actually says
Legacy tokens policy
packages/tokens(@adobe/spectrum-tokens) is a generated legacy output kept for existing npm consumers.packages/design-datais the source of truth.- New tooling, SDK code, and docs must not import
@adobe/spectrum-tokensor readpackages/tokens/{src,schemas,naming-exceptions.json,manifest.json}. Load the cascade data (packages/design-data) instead; for the legacy set shape, project it withdesign-data migrate legacy-outputordesign_data_core::legacy. - Token-type schemas live in
packages/design-data-spec/schemas/andnaming-exceptions.jsoninpackages/design-data/. The copies inpackages/tokensanddocs/site/public/schemasare generated: runnode packages/design-data-spec/scripts/sync-token-schemas.mjs(drift check:moon run design-data-spec:check). moon run root:check-legacy-consumersfails on new references. Intentional uses (legacy-output, diff and release tooling, parity tests, old-tag fallbacks) go inscripts/legacy-consumers.allowlist.jsonwith a reason; temporary entries cite their bead id.
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.
- yesterday First seen · 16 lines · 0 tokens per session scan A fc1375d7594b
legacy-tokens is a cursor rule published in the GitHub repository adobe/spectrum-design-data (156 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 346 tokens. 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-10-17.
Other cursor rules, from other repositories
cursorrules
You are using StyleSeed, a design-method engine whose goal is to make expert design judgment repeatable by coding agents, not to replace designers with aesthetic preferences. Preserve approved project choices; report unsupported choices instead of silently restyling the project's design system. PRODUCT-PRINCIPLES.md…
taste-enforcement
These dials drive all downstream decisions. Adjust per-prompt when the user specifies a different mood.
design-animation-rules
Taste is trained, not innate. Reverse engineer animations. Inspect interactions. Unseen details compound — a thousand barely audible voices all singing in tune. Beauty is leverage.
mimic-ai
Golden workflow for building or editing Figma designs with the Mimic AI MCP server (mimicstatus, mimicdiscoverds, figmacreateframe, figmainsertcomponent, mimicbuildtable, mimicbuildchart, and related tools).
sigil-conventions
All CSS variables use the --s- prefix: var(--s-primary), var(--s-surface), etc.
mcp-tools
Rules for adding or modifying MCP tools in src/mcp/server.ts.