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/aa-on-ai/agentic-design-system/agents-mdgit clone --depth 1 https://github.com/aa-on-ai/agentic-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/aa-on-ai/agentic-design-system/agents-md)<a href="https://agentmods.dev/instructions/aa-on-ai/agentic-design-system/agents-md"><img src="https://agentmods.dev/badge/instructions/aa-on-ai/agentic-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.1 | $0.00741 | $0.00741 |
| Opus 5 | $0.00370 | $0.00370 |
| Sonnet 5 | $0.00148 | $0.00148 |
| Haiku 4.5 | $0.00074 | $0.00074 |
Grade A, and why
agentic-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 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.
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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agentic design system — agent instructions
start here
for any "help me design or review some UI" task, start at
workflows/create-design-workflow.md. it routes you into
the right profile or workflow by intent. the runbooks in workflows/ are runnable
wrappers around the routing logic below.
skills
this repo contains 10 design skills: one orchestrator plus core, reference, production, and creative packs.
orchestrator (read first for visual work):
skills/agentic-design-system/— routing, gate order, verification expectations
core pack (always active for visual work):
skills/design-review/— quality gate with verification scripts and 11 reference filesskills/ux-baseline-check/— state completeness (loading, empty, error)skills/ui-polish-pass/— final visual polish pass
production pass (for public sites and products):
skills/agent-friendly-design/— make sites work for AI consumers
reference gate (opt-in before coding):
skills/visual-reference-calibration/— reference contract for screenshots, sites, CodePens, or "make it feel like this" work
creative pack (opt-in only — read each skill's trigger rules before using):
skills/whimsical-design/— personality and delightskills/world-build/— immersive atmosphereskills/web-animation-design/— motion and interaction feel
routing
read routing/ROUTING.md before starting any visual task. it tells you:
- when to use core pack only (default for most work)
- when to add creative pack skills (only when triggered)
- when to skip entirely (non-visual work)
verification
two tiers — see skills/design-review/scripts/README.md.
pre-flight (source heuristics, gameable). cheap grep over source; catch obvious defaults early:
python3 skills/design-review/scripts/anti-pattern-check.py <your-file.tsx>
python3 skills/design-review/scripts/state-check.py <your-file.tsx>
python3 skills/design-review/scripts/accessibility-check.py <your-file.tsx>
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.
- 6d ago First seen · 71 lines · 741 tokens per session scan A 0767672625d9
agentic-design-system AGENTS.md is an instructions file published in the GitHub repository aa-on-ai/agentic-design-system (5 stars, last pushed 16d ago), licensed MIT. It adds 741 tokens to every session, about $0.0037 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).
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 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).
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.