spectrum-design-data AGENTS.md

spectrum-design-data AGENTS.md is an instructions file for Codex, OpenCode from adobe/spectrum-design-data. It costs 526 tokens per session, scanned C, original, Apache-2.0.

Project instructions for agents working in Adobe Spectrum Design Data. They describe the repository’s issue-tracking process, shell rules, and how an agent should finish a work session.

In plain words
What is it for?
Use them when claiming or closing issues, recording project knowledge, running shell commands, or completing work in this repository.
Why use it?
They keep task tracking and file operations consistent and reduce the risk of using unsafe or unsupported project workflows.

Instructions file for CodexOpenCode

About the project

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.

adobe/spectrum-design-data · 151 stars · on GitHub

Install

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.

agentmods
npx agentmods add instructions/adobe/spectrum-design-data/agents-md
Clone the repo
git clone --depth 1 https://github.com/adobe/spectrum-design-data

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for spectrum-design-data AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/adobe/spectrum-design-data/agents-md.svg)](https://agentmods.dev/instructions/adobe/spectrum-design-data/agents-md)
Your own site
<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>
Per session 526 This file is loaded in full into every session.
When invoked 526 The same file — it is already loaded in full.
Security scan C 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured yesterday against content hash ea83f8a5eeeb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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
Origin

Copies of this mod

8 near-identical copies found in the catalogue:

AGENTS.md · 57 lines

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 bd for ALL task tracking — do NOT use TodoWrite, TaskCreate, or markdown TODO lists
  • Run bd prime for detailed command reference and session close protocol
  • Use bd remember for 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=yes for non-interactive
  • ssh - use -o BatchMode=yes to fail instead of prompting
  • apt-get - use -y flag
  • brew - use HOMEBREW_NO_AUTO_UPDATE=1 env var

Session Completion

When ending a work session, you MUST complete ALL steps below. Work is NOT complete until git push succeeds.

  1. File issues for remaining work — create issues for anything that needs follow-up
  2. Run quality gates (if code changed) — tests, linters, builds
  3. Update issue status — close finished work, update in-progress items
  4. Push to remote — this is MANDATORY:
    git pull --rebase
    bd dolt push
    git push
    git status  # MUST show "up to date with origin"
    
  5. Verify — all changes committed and pushed

Read the full file on GitHub · 57 lines

Changes

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.

  1. yesterday First seen · 57 lines · 526 tokens per session scan C ea83f8a5eeeb

Subscribe to this mod's changes

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.