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/rust-sdk)<a href="https://agentmods.dev/rules/adobe/spectrum-design-data/rust-sdk"><img src="https://agentmods.dev/badge/rules/adobe/spectrum-design-data/rust-sdk/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/rust-sdk"><img src="https://agentmods.dev/badge/rules/adobe/spectrum-design-data/rust-sdk.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.00247 |
| Opus 5.5 | $0.00000 | $0.00099 |
| Sonnet 5.5 | $0.00000 | $0.00049 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
rust-sdk 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
Rust SDK
- Run build, test, and lint through moon, not cargo directly:
moon run sdk:build,moon run sdk:test,moon run sdk:lint,moon run sdk:fmt. - Tests run with
cargo nextest; doctests run separately withmoon run sdk:test-doc. - The toolchain is pinned in
sdk/rust-toolchain.toml; don't override it. - New Rust files start with
// Copyright YYYY Adobe. All rights reserved.using the current year. sdk/coreembeds token and guideline data at compile time. After editing JSON underpackages/design-data/, runmoon run sdk:codegen, thenmoon run sdk:codegen-check.- Never read into
sdk/target/; it is large and gitignored.
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 · 18 lines · 0 tokens per session scan A 7fc0955e5134
rust-sdk 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 247 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
typescript-conventions
Label console.warn and console.error calls with their origin.
python_tests
We use the unit tests to cover internal behavior that can work without the web / backend counterpart. We aim for 95%+ unit test coverage of our Python code in lib/streamlit.
atmos-rules
This is a Golang CLI project using Cobra for command structure and Viper for configuration management. The project maintains high code quality standards through golangci-lint and aims for maximum test coverage. The repository also includes the website source code for https://atmos.tools.
mockito
This guide provides definitive best practices for writing robust, maintainable, and readable unit tests using Mockito with JUnit 5, focusing on modern patterns and common pitfalls.
20-testing-generated-and-structure
Testing expectations, generated-file boundaries, and CLI structure contract.
fix-galo
SYNTAX RULES.