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/khalidabdi1/design-ai/agents-mdgit clone --depth 1 https://github.com/Khalidabdi1/design-aiWrote 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/khalidabdi1/design-ai/agents-md)<a href="https://agentmods.dev/instructions/khalidabdi1/design-ai/agents-md"><img src="https://agentmods.dev/badge/instructions/khalidabdi1/design-ai/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.00337 | $0.00337 |
| Opus 5 | $0.00169 | $0.00169 |
| Sonnet 5 | $0.00067 | $0.00067 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
design-ai 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.
What it actually says
AGENTS.md - design-ai
How to Add a New Company
# 1. Create directory
mkdir design-md/[company-name]/
# 2. Fetch target website
webfetch https://[company].com
# 3. Create DESIGN.md (see format below)
# 4. Commit and push
git add design-md/[company-name]/
git commit -m "Add [Company] design system docs"
git push
DESIGN.md Format (9 sections)
Every file must follow this structure:
- Visual Theme & Atmosphere - Mood, density, aesthetic philosophy
- Color Palette & Roles - Token name + hex + functional role
- Typography Rules - Font stack, type scale table
- Component Stylings - Buttons, cards, inputs with CSS snippets
- Layout Principles - Spacing scale, grid, responsive approach
- Depth & Elevation - Shadow system, surface hierarchy
- Do's and Don'ts - Design guardrails
- Responsive Behavior - Breakpoints, touch targets
- Agent Prompt Guide - Quick reference + prompt snippet
Use the webfetch tool to collect colors, typography, and components directly from each company's live website.
Directory Structure
design-md/
├── company-1/DESIGN.md
├── company-2/DESIGN.md
└── ... (38 companies total)
Git Conventions
- Commit message:
"Add [Company] design system docs" - No branch protection - push directly to main
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 · 48 lines · 337 tokens per session scan A 5a4a44d6ba43
design-ai AGENTS.md is an instructions file published in the GitHub repository Khalidabdi1/design-ai (233 stars, last pushed yesterday), licensed MIT. It adds 337 tokens to every session, about $0.0017 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-30.
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.
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.
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).
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.