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/changesets)<a href="https://agentmods.dev/rules/adobe/spectrum-design-data/changesets"><img src="https://agentmods.dev/badge/rules/adobe/spectrum-design-data/changesets/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/changesets"><img src="https://agentmods.dev/badge/rules/adobe/spectrum-design-data/changesets.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.00240 |
| Opus 5.5 | $0.00000 | $0.00096 |
| Sonnet 5.5 | $0.00000 | $0.00048 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
changesets 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 2d 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.
What it actually says
Changesets
-
Create a changeset for every user-facing change; never edit package versions by hand.
-
Bump level:
patchfor a bug fix or packaging fix,minorfor additive or validation-behavior changes,majorfor breaking changes. -
The body is at most 20 lines: one intro sentence plus one bullet per changed artifact. Put rationale in the PR description.
-
Format:
Short summary (closes #NNN). - **path/to/file**: what changed and why it matters. -
Write the file directly rather than using the interactive
pnpm changesetwizard when working non-interactively. -
Verify with
node tools/changeset-linter/src/cli.js check --fail-on-warnings.
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.
- 2d ago First seen · 29 lines · 0 tokens per session scan A 27a0a3b358af
changesets is a cursor rule published in the GitHub repository adobe/spectrum-design-data (156 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 240 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-14.
Other cursor rules, from other repositories
08-github-workflow-standards
GitHub issue/PR/milestone standards for Matryca Plumber (OSS maintainer rigor).
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
agent-routing
Route work to sys-arch, sys-engineer, sys-release, sys-review. Every PR needs a SemVer bump and changelog.
dev-workflow
Monorepo developer workflow standards - mise tasks, git hooks, CI/CD, release automation.
version-and-issues
Version & issue tracking — every change gets a SemVer class, an issue with the matching type: label, a major/minor milestone, and a card on the configured project board (project.config.yaml).
github-repo-triage
Triage and maintain GitHub repos — issues, PRs, cherry-picks, releases, publishing.