spectrum-design-data: Instructions file for Codex

AGENTS.md

spectrum-design-data AGENTS.md is an instructions file for Codex, OpenCode from adobe/spectrum-design-data. It costs 1,605 tokens per session, scanned C, a copy of awesome-spain AGENTS.md, 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 ✓ vendor

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions CLAUDE.md; names the TodoWrite tool; mentions AGENTS.md.

This is adobe/spectrum-design-data's own configuration. It tells Codex and OpenCode how to work on spectrum-design-data itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything spectrum-design-data configures →

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 · 156 stars · on GitHub · opensource.adobe.com

Reuse

Borrowing it

Nothing to install: this file belongs to adobe/spectrum-design-data. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/adobe/spectrum-design-data/main/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/github.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/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.

agentmods 80×15 button for spectrum-design-data AGENTS.md

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,605 This file is loaded in full into every session.
When invoked 1,605 The same file — it is already loaded in full.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 69% copy Near-identical to another mod 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.1 $0.01605 $0.01605
Opus 5.5 $0.00642 $0.00642
Sonnet 5.5 $0.00321 $0.00321
Haiku 4.5 $0.00161 $0.00161

Measured 6d ago against content hash 0721ce220b54, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 6d 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.

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

This is a copy

69% identical to awesome-spain AGENTS.md — 136 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

AGENTS.md · 112 lines

How it starts

The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Instructions

Canonical instructions for every AI tool in this repository. CLAUDE.md files only point here. Package-level AGENTS.md files add local commands; docs/repo-index.md lists every project with its audience and lifecycle.

Shared rules and skills live in .ai/ (see .ai/README.md). Edit them there, then run pnpm ai:sync. Never edit .github/instructions/, .cursor/rules/, or the .claude//.cursor/ symlinks by hand.

Repository Rules

  • [email protected] only (never npm or yarn); moon for tasks (moon run <project>:<task>, moon query projects); AVA for JS tests; Node ~20.12; ESM throughout.
  • Changesets: pnpm changeset for every user-facing change. Body ≤ 20 lines; verify with node tools/changeset-linter/src/cli.js check --fail-on-warnings. Details: .ai/rules/changesets.md.
  • Conventional commits (type(scope): description, ! for breaking), enforced by commitlint.
  • Copyright: every new file starts with Copyright YYYY Adobe. All rights reserved. (current year, language-appropriate comment style). License: Apache-2.0.
  • Code style: 2-space indent, single quotes in docs examples, const over let, async/await. See .ai/rules/javascript.md.
  • Tests: moon run test (all), pnpm --filter <package> test (one), moon run sdk:test (Rust).
  • GitHub: use the gh CLI. Fill every section of .github/PULL_REQUEST_TEMPLATE.md; link issues and describe how you tested.
  • Layout: packages/ core libraries, tools/ internal tooling, docs/ sites and explorers, sdk/ Rust workspace, platforms/ incubating platform manifests.

Maintainer Workflows

The rest of this file covers maintainer tooling (Beads, Scout, Jira, session close). It isn't needed to contribute to a package.

Issue tracking

This project uses bd (beads) for issue tracking. Run bd prime for full workflow context and commands.

Read the full file on GitHub · 112 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. 6d ago Changed · +42 lines · +930 tokens per session 0721ce220b54
  2. 1mo ago Changed · +13 lines · +149 tokens per session 007925086e8a
  3. 1mo ago 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 (156 stars, last pushed today), licensed Apache-2.0. It adds 1,605 tokens to every session, about $0.0064 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). It is 69% identical to awesome-spain AGENTS.md, differing in 136 lines, and is treated as a copy.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,649 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,257 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,159 tokens