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 agentmods add skills/adobe/spectrum-design-data/enhance-sync-prnpx skills add adobe/spectrum-design-data --skill enhance-sync-prgit 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/enhance-sync-pr)<a href="https://agentmods.dev/skills/adobe/spectrum-design-data/enhance-sync-pr"><img src="https://agentmods.dev/badge/skills/adobe/spectrum-design-data/enhance-sync-pr.svg" alt="Measured on agentmods" 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.00099 | $0.01606 |
| Opus 5 | $0.00049 | $0.00803 |
| Sonnet 5 | $0.00020 | $0.00321 |
| Haiku 4.5 | $0.00010 | $0.00161 |
Grade A, and why
enhance-sync-pr 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.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enhance sync PR (Tokens Studio → spectrum-design-data)
When this applies
- PR opened by
mrcjhicksfromtokens-sync/patch-spectrum2-from-main(or similar sync branch). - Body links to
github.com/adobe/spectrum-tokens-studio-data/actions/runs/…. - CI red after sync (validation, snapshot, component props, wireframe, etc.).
- Changeset missing; title still
feat: updates from spectrum-tokens-studio-dataor duplicatedfeat: Feat:.
Repo and tools
- Monorepo root: workspace root (
spectrum-design-data). - Changeset generator:
tools/token-changeset-generator— fetches source PR motivation, runstdiff, infers semver bump. - Automation:
.github/workflows/enhance-sync-pr.ymland.github/actions/extract-source-pr-info.
1. Resolve source PR
From the design-data PR body, take the spectrum-tokens-studio-data Actions run URL or the Tokens Studio PR link.
gh pr view <N> --repo adobe/spectrum-design-data --json body,title,headRefName,url
If only the run URL exists, resolve merged PR from that run (same logic as extract-source-pr-info).
Record:
- Source PR URL (e.g.
https://github.com/adobe/spectrum-tokens-studio-data/pull/297) - Source author (
user.loginfrom that PR) for attribution
gh api repos/adobe/spectrum-tokens-studio-data/pulls/<num> --jq '{title, author: .user.login, body}'
2. Diagnose CI (suggest fixes; user approves edits)
Check out the PR branch with full history (fetch-depth: 0) so tdiff can compare to main.
Run in order:
moon run tokens:validateDesignData
moon run tokens:verifyDesignDataSnapshot
cd packages/tokens && pnpm ava
Or full graph: moon ci (same as GitHub Actions).
Failure map (what to suggest)
| Symptom | Likely cause | Suggestion | ||
|---|---|---|---|---|
checkComponentProps lists token names |
Missing or wrong component on entries in color-component.json, layout-component.json, or icons.json |
Set component to match token name prefix (see packages/tokens/test/checkComponentProps.js). |
||
Schema / color-set errors |
sets missing light, dark, or wireframe |
Align with schemas/token-types/color-set.json. |
||
verifyDesignDataSnapshot / snapshot mismatch |
Validation report changed vs golden file | Paths in the snapshot are relative to packages/tokens/. After moon run sdk:build, run migrate snapshot from packages/tokens/ so paths match moon run tokens:verifyDesignDataSnapshot: cd packages/tokens && ../../sdk/target/debug/design-data migrate snapshot ./src --output ./snapshots/validation-snapshot.json --schema-path ./schemas --exceptions-path ./naming-exceptions.json. |
||
Token file / $schema / uuid |
Invalid token shape | Fix per token-file.json and failing AVA tests. |
||
| Alias / renamed / manifest | Broken refs or manifest drift | Fix aliases; run moon run tokens:buildManifest. |
||
| Changeset lint on PR | Bad frontmatter | Valid --- / "@adobe/spectrum-tokens": patch | minor | major / body. |
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 · 136 lines · 99 tokens per session scan A 1c29b912734d
enhance-sync-pr is a skill published in the GitHub repository adobe/spectrum-design-data (151 stars, last pushed today), licensed Apache-2.0. It adds 99 tokens to every session and 1,606 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
ss-studio
Turn a product brief and optional references into three distinct creative directions, a human-selected StyleSeed interaction plan, generated image/video asset jobs, a working UI prototype, and a verified prototype-first showcase reel. Use for client concepts, app interaction exploration, trendy but coherent UI…
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
ss-copy
Generate UX microcopy (button labels, error messages, empty states, toasts) following a casual-but-polite voice and tone.
ss-lint
Quick automated lint — detects common design system violations in seconds.
omd-apply
프로젝트 DESIGN.md를 UI/시각 작업의 brand context로 적용. 컴포넌트·색상·폰트·레이아웃 수정 같은 구체적 요청과 톤·분위기 표현 — KR '좀 더 따뜻하게', EN 'make it warmer/cooler', 日本語「もう少し暖かく」, 繁體中文「更溫暖一點」 — 모두에 트리거. DESIGN.md 부재 시 omd:init 우선. 화면 전체 신규 디자인은 omd:harness, 교정 기록은 omd:remember.
omd:autopilot
One-prompt autonomous product design and implementation. Use automatically for broad greenfield UI requests such as 'from scratch', '새 제품/화면을 알아서 만들어줘', or requests that delegate DESIGN.md creation. It decides whether to reuse, establish, refresh, or skip a project design system; asks at most one consequential…