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/antdv-next/skills/agents-mdgit clone --depth 1 https://github.com/antdv-next/skillsWrote 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/antdv-next/skills/agents-md)<a href="https://agentmods.dev/instructions/antdv-next/skills/agents-md"><img src="https://agentmods.dev/badge/instructions/antdv-next/skills/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.00609 | $0.00609 |
| Opus 5 | $0.00304 | $0.00304 |
| Sonnet 5 | $0.00122 | $0.00122 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
skills 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 4d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
This repository generates a single-language Antdv Next skill package from the upstream playground docs and demos. Outputs live under skills/antdv-next/ and are regenerated via esno scripts.
Project Structure & Module Organization
scripts/: TypeScript generator (scripts/generate-antdv-next-skill.ts) that builds the skill references.skills/antdv-next/: Generated skill output, includingSKILL.md,GENERATION.md, andreferences/.skills/antdv-next/references/: Copied docs and demo markdown (components/**,docs/vue/**).repos/antdv-next/: Git submodule with the upstream Antdv Next source (used as input for generation).package.json: Local scripts and dev dependencies for generation.
Build, Test, and Development Commands
pnpm run generate:zh: Generate Chinese references andSKILL.md.pnpm run generate:en: Generate English references andSKILL.md.pnpm run generate: Alias for Chinese generation.
These commands read from repos/antdv-next and rewrite docs/demos into skills/antdv-next/references/.
Coding Style & Naming Conventions
- Language: TypeScript (
.ts) with ESM ("type": "module"). - Indentation: 2 spaces; keep lines concise and avoid excessive blank lines.
- Naming:
kebab-casefor markdown filenames;camelCasefor variables/functions. - Tools:
esnoexecutes TypeScript directly; keep generator logic deterministic and idempotent.
Testing Guidelines
There are no automated tests in this repo. Validate changes by running a generate command and spot-checking:
skills/antdv-next/GENERATION.mdskills/antdv-next/SKILL.md- A few sample docs and demos under
skills/antdv-next/references/
Commit & Pull Request Guidelines
No strict commit convention is enforced. Use clear, imperative commit messages (e.g., “Update generator link rewrites”). PRs should include:
- A short summary of changes
- The command used to regenerate references
- Any notable behavior changes (e.g., removed sections, link rewrites)
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.
- 4d ago First seen · 52 lines · 609 tokens per session scan A b76f52918709
skills AGENTS.md is an instructions file published in the GitHub repository antdv-next/skills (10 stars, last pushed 2mo ago), licensed MIT. It adds 609 tokens to every session, about $0.0030 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).
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.