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/antd-skill/agents-mdgit clone --depth 1 https://github.com/ant-design/antd-skillWrote 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/ant-design/antd-skill/agents-md)<a href="https://agentmods.dev/instructions/ant-design/antd-skill/agents-md"><img src="https://agentmods.dev/badge/instructions/ant-design/antd-skill/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.00318 | $0.00318 |
| Opus 5 | $0.00159 | $0.00159 |
| Sonnet 5 | $0.00064 | $0.00064 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
antd-skill 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.
What it actually says
Ant Design Skills - Agent Guide
Generate and maintain Agent Skills for the Ant Design ecosystem.
Core principles
- Focus on agent decision-making and practical usage patterns.
- Avoid end-user tutorials, getting-started steps, and obvious basics.
- Do not invent APIs or rely on undocumented behaviors.
- Keep
SKILL.mdconcise; move advanced detail toreferences/*.md. - Prefer short, focused examples when needed.
Repo structure
.
└── skills/
├── ant-design/
│ ├── SKILL.md
│ └── references/
Scope by skill
- ant-design: antd v6 + React 18-19, component selection, theming/tokens, SSR, a11y, performance, plus Pro 5 layouts/routing/access/CRUD and X (AI/chat UI) patterns.
Updating skills
- Read the existing
SKILL.mdand relevantreferences/*.mdfirst. - Keep the main skill as a decision guide; add new details as references.
- Add or update reference files with kebab-case names.
- Update the
Referenceindex table inSKILL.mdwhen adding references. - Ensure version scope and assumptions are explicit and consistent.
Adding a new skill
- Create
skills/<name>/SKILL.mdandskills/<name>/references/. - Include a clear scope, process, and output format in
SKILL.md. - Keep references short and task-oriented.
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 · 40 lines · 318 tokens per session scan A bf8d984710ff
antd-skill AGENTS.md is an instructions file published in the GitHub repository ant-design/antd-skill (133 stars, last pushed 5mo ago), licensed MIT. It adds 318 tokens to every session, about $0.0016 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.
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.