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/ant-design/ant-design-cli/agents-mdgit clone --depth 1 https://github.com/ant-design/ant-design-cliWhat 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.01922 | $0.01922 |
| Opus 5 | $0.00961 | $0.00961 |
| Sonnet 5 | $0.00384 | $0.00384 |
| Haiku 4.5 | $0.00192 | $0.00192 |
Grade A, and why
ant-design-cli 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to Codex (Codex.ai/code) when working with code in this repository.
Coding Principles
Principles inspired by andrej-karpathy-skills. Bias toward caution over speed. For trivial tasks, use judgment.
1. Think Before Coding
Don't assume. Don't hide confusion. Surface tradeoffs.
- State your assumptions explicitly. If uncertain, ask.
- If multiple interpretations exist, present them — don't pick silently.
- If a simpler approach exists, say so. Push back when warranted.
- If something is unclear, stop. Name what's confusing. Ask.
2. Simplicity First
Minimum code that solves the problem. Nothing speculative.
- No features beyond what was asked.
- No abstractions for single-use code.
- No "flexibility" or "configurability" that wasn't requested.
- No error handling for impossible scenarios.
- If you write 200 lines and it could be 50, rewrite it.
Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify.
3. Surgical Changes
Touch only what you must. Clean up only your own mess.
When editing existing code:
- Don't "improve" adjacent code, comments, or formatting.
- Don't refactor things that aren't broken.
- Match existing style, even if you'd do it differently.
- If you notice unrelated dead code, mention it — don't delete it.
When your changes create orphans:
- Remove imports/variables/functions that YOUR changes made unused.
- Don't remove pre-existing dead code unless asked.
The test: Every changed line should trace directly to the user's request.
4. Goal-Driven Execution
Define success criteria. Loop until verified.
Transform tasks into verifiable goals:
- "Add validation" → "Write tests for invalid inputs, then make them pass"
- "Fix the bug" → "Write a test that reproduces it, then make it pass"
- "Refactor X" → "Ensure tests pass before and after"
For multi-step tasks, state a brief plan:
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 · 184 lines · 1,922 tokens per session scan A 2ba834d8da8a
ant-design-cli AGENTS.md is an instructions file published in the GitHub repository ant-design/ant-design-cli (252 stars, last pushed 3d ago), licensed MIT. It adds 1,922 tokens to every session, about $0.0096 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
ant-design-pro CLAUDE.md
Claude Code instructions for ant-design/ant-design-pro, covering claude.md, project, commands, critical rules and architecture essentials.
skyroc AGENTS.md
Instructions for Ohh-889/skyroc, covering agents.md, 规范索引, skills 调用规则(关键), 思考顺序 and react 组件规范.
south-admin-react CLAUDE.md
Instructions for southliu/south-admin-react, covering claude.md, commands, development, code quality and package management.
south-admin-react AGENTS.md
Instructions for southliu/south-admin-react, covering agents.md, 常用命令, 新建页面(重要约定), 目录结构 and 路由(自动生成).
pinyin AGENTS.md
Instructions for yunsii/pinyin, covering agents.md, hard rules, 方案与文本靠 side-effect 注册,漏 import 等于没加, vite.config.ts 的 base: '/pinyin/' 不要随手改 and 拼音术语变量名用全拼.
ant-design-pro AGENTS.md
AGENTS.md instructions for ant-design/ant-design-pro, a project described as: 👨🏻💻👩🏻💻 Use Ant Design like a Pro!