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 instructions/adobe/spectrum-design-data/agents-mdgit 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/instructions/adobe/spectrum-design-data/agents-md)<a href="https://agentmods.dev/instructions/adobe/spectrum-design-data/agents-md"><img src="https://agentmods.dev/badge/instructions/adobe/spectrum-design-data/agents-md.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 | $0.00526 | $0.00526 |
| Opus 5 | $0.00263 | $0.00263 |
| Sonnet 5 | $0.00105 | $0.00105 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade C, and why
spectrum-design-data AGENTS.md scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf directory # NOT: rm -r directory Copies of this mod
8 near-identical copies found in the catalogue:
- alluvium AGENTS.md — 88% identical, 66 lines differ
- comfyui-mcp AGENTS.md — 88% identical, 52 lines differ
- tuxevil-rotator AGENTS.md — 88% identical, 52 lines differ
- hgm AGENTS.md — 88% identical, 66 lines differ
- minirag-mcp AGENTS.md — 88% identical, 66 lines differ
- claude-mountaineering-skills AGENTS.md — 88% identical, 66 lines differ
- skills AGENTS.md — 88% identical, 52 lines differ
- tasks AGENTS.md — 88% identical, 54 lines differ
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
This project uses bd (beads) for issue tracking. Run bd prime for full workflow context and commands.
Quick Reference
bd ready # Find available work
bd show <id> # View issue details
bd update <id> --claim # Claim work atomically
bd close <id> # Complete work
bd dolt push # Push beads data to remote
Rules
- Use
bdfor ALL task tracking — do NOT use TodoWrite, TaskCreate, or markdown TODO lists - Run
bd primefor detailed command reference and session close protocol - Use
bd rememberfor persistent knowledge — do NOT use MEMORY.md files
Non-Interactive Shell Commands
ALWAYS use non-interactive flags with file operations to avoid hanging on confirmation prompts.
Shell commands like cp, mv, and rm may be aliased to include -i (interactive) mode on some systems, causing the agent to hang indefinitely waiting for y/n input.
Use these forms instead:
cp -f source dest # NOT: cp source dest
mv -f source dest # NOT: mv source dest
rm -f file # NOT: rm file
rm -rf directory # NOT: rm -r directory
cp -rf source dest # NOT: cp -r source dest
Other commands that may prompt:
scp- use-o BatchMode=yesfor non-interactivessh- use-o BatchMode=yesto fail instead of promptingapt-get- use-yflagbrew- useHOMEBREW_NO_AUTO_UPDATE=1env var
Session Completion
When ending a work session, you MUST complete ALL steps below. Work is NOT complete until git push succeeds.
- File issues for remaining work — create issues for anything that needs follow-up
- Run quality gates (if code changed) — tests, linters, builds
- Update issue status — close finished work, update in-progress items
- Push to remote — this is MANDATORY:
git pull --rebase bd dolt push git push git status # MUST show "up to date with origin" - Verify — all changes committed and pushed
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 · 57 lines · 526 tokens per session scan C ea83f8a5eeeb
spectrum-design-data AGENTS.md is an instructions file published in the GitHub repository adobe/spectrum-design-data (151 stars, last pushed yesterday), licensed Apache-2.0. It adds 526 tokens to every session, about $0.0026 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other instructions, from other repositories
montology CLAUDE.md
Claude Code instructions for shinyobjectz/montology, covering montology — repo instructions, the shape and ground rules.
Sigil-UI AGENTS.md
Instructions for Kevin-Liu-01/Sigil-UI, covering sigil ui — agent instructions, the #1 rule, how it works, quick reference: what to edit for common tasks and repository structure.
design-md-extractor CLAUDE.md
Instructions for jpoindexter/design-md-extractor, covering claude.md, commands, run a single test file, cli usage (after build) and architecture.
Design-Learn CLAUDE.md
Instructions for GalaxyXieyu/Design-Learn, covering claude.md, todo, quick start, server and vscode extension.
design-pipeline CLAUDE.md
Claude Code instructions for 2233admin/design-pipeline, a project described as: 给 AI Agent 的前端设计管线:先写 DESIGN.md 与 MOTION.md,经 job 分发、OpenSpec 与证据门禁再写代码。.
Standby.Design CLAUDE.md
Claude Code instructions for KarstenKreh/Standby.Design, covering claude.md, npm publish (standby-design-mcp), deploys (website + remote mcp server) and pitfalls.