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/pr-reviewgit 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/pr-review)<a href="https://agentmods.dev/instructions/iress/design-system/pr-review"><img src="https://agentmods.dev/badge/instructions/iress/design-system/pr-review.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.1 | $0.03034 | $0.03034 |
| Opus 5 | $0.01517 | $0.01517 |
| Sonnet 5 | $0.00607 | $0.00607 |
| Haiku 4.5 | $0.00303 | $0.00303 |
Grade A, and why
design-system pr-review.instructions.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 5d 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Review Instructions
Coding standards, domain knowledge, and preferences that AI should follow when reviewing pull requests.
AI Context & Documentation Freshness Checks
When reviewing a PR, always verify that AI-facing documentation stays in sync with code changes. Flag any missing updates as required changes (not suggestions).
Sandbox Dependency Tags
Trigger: Any PR that modifies CodeSandbox examples, Storybook sandbox defaults, or docs/snippets that generate package.json files for sandbox usage.
What to verify:
- IDS v6 sandbox examples use the current prerelease tag:
@iress-oss/ids-components: 'beta'and@iress-oss/ids-tokens: 'beta'when tokens are installed directly. - Review generated sandbox dependencies in Storybook previews, sandbox stories, mock stories, helper utilities, and README/MDX examples — not just the visible docs page.
- Flag any use of
alphafor IDS sandbox dependencies unless the PR explicitly documents a temporary rollback and explains why.
Review comment template:
This PR updates a CodeSandbox or Storybook sandbox example but still references IDS
alphapackages. IDS v6 sandboxes should use thebetatag for@iress-oss/ids-componentsand@iress-oss/ids-tokensso generated examples install the current prerelease.
1. Token Schema — packages/tokens/.ai/index.json
Trigger: Any PR that modifies files under packages/tokens/src/schema/ or changes the design token build pipeline (packages/tokens/src/generated/, token transforms, or token build config).
What to verify:
- If a new token category is introduced,
packages/tokens/.ai/index.jsonhas a new entry intokenCategorieswith the correctname,description,schemaSource, andcssVariablePrefix. - If a token category is removed, its entry is deleted from
tokenCategories. - If token values, descriptions, or structure change significantly, verify that the
descriptionfields inindex.jsonstill accurately reflect the token category.
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.
- 5d ago First seen · 187 lines · 3,034 tokens per session scan A 78c03f5b54ef
design-system pr-review.instructions.md is an instructions file published in the GitHub repository iress/design-system (1 stars, last pushed 2d ago), licensed Apache-2.0. It adds 3,034 tokens to every session, about $0.0152 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
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.
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.
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.
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).