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/iress/design-system/agents-mdgit clone --depth 1 https://github.com/iress/design-systemWrote 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/iress/design-system/agents-md)<a href="https://agentmods.dev/instructions/iress/design-system/agents-md"><img src="https://agentmods.dev/badge/instructions/iress/design-system/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.01299 | $0.01299 |
| Opus 5 | $0.00649 | $0.00649 |
| Sonnet 5 | $0.00260 | $0.00260 |
| Haiku 4.5 | $0.00130 | $0.00130 |
Grade A, and why
design-system AGENTS.md 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Iress Design System (IDS) monorepo — React component library and design tokens for Iress products.
Setup
corepack enable
yarn
yarn prepare # installs husky hooks and builds all packages
Node 22, Yarn 4 (Berry). The packageManager field in package.json pins the exact Yarn version; corepack enable is required to activate it.
⚠️ Long-running commands — never run in agent workflows
Any dev, test (without :coverage), or watch command starts a persistent process that never exits. Always use these non-blocking alternatives:
| Instead of | Use |
|---|---|
yarn dev / yarn storybook |
yarn build (one-shot build) |
yarn workspace ... run test |
yarn workspace ... run test:coverage (runs once and exits) |
Build
yarn build # builds all packages (topological order) then runs translate scripts
The yarn monorepo alias runs yarn workspaces foreach -Ai --topological-dev --exclude=@iress/design-system-monorepo. Use it for cross-package commands.
Testing
yarn test:coverage # all packages, with coverage
yarn test:ci # coverage + threshold check
# single package
yarn workspace @iress-oss/ids-components run test:coverage
# single file
yarn workspace @iress-oss/ids-components run test:coverage Button.test.tsx
Tests use Vitest. Test startup can take 30+ seconds — this is normal, not a failure. Wait for explicit PASS/FAIL output.
Test files must live inside each package's src/ directory. Do not create tests for pure interface/type files with no runtime behavior.
Type checking
yarn typecheck # all packages
Bundle size
yarn size # check all packages against budgets
yarn size:check # same, but JSON output (useful for scripting)
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.
- 3d ago First seen · 125 lines · 1,299 tokens per session scan A 56b496591e87
design-system AGENTS.md is an instructions file published in the GitHub repository iress/design-system (1 stars, last pushed 7d ago), licensed Apache-2.0. It adds 1,299 tokens to every session, about $0.0065 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-08-31.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.