Borrowing it
Nothing to install: this file belongs to Avinava/document-design-system. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Avinava/document-design-system/main/AGENTS.mdgit clone --depth 1 https://github.com/Avinava/document-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/avinava/document-design-system/agents-md)<a href="https://agentmods.dev/instructions/avinava/document-design-system/agents-md"><img src="https://agentmods.dev/badge/instructions/avinava/document-design-system/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/avinava/document-design-system/agents-md"><img src="https://agentmods.dev/badge/instructions/avinava/document-design-system/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.01116 | $0.01116 |
| Opus 5.5 | $0.00446 | $0.00446 |
| Sonnet 5.5 | $0.00223 | $0.00223 |
| Haiku 4.5 | $0.00112 | $0.00112 |
Grade A, and why
document-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 9d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository guidance
This repository treats document design as two independent axes:
- Document pattern controls reading structure and is declared with
data-pattern. - Theme controls visual voice through semantic tokens and is declared with
data-theme.
Do not reduce the writing examples to one generic longform layout. Select one
of the eleven patterns in core/document-patterns.md, then use the modules that
support that reader movement. Keep prose readable at 62–72 characters while
allowing maps, tables, comparisons, timelines, and registers to use the wider
shell.
Markdown in examples/<slug>.md is the canonical repository-friendly form.
Designed HTML is generated from templates/types/<slug>.html (presets) or
templates/composed/<slug>.html (composed examples); both forms must use the
same title and factual anchors from examples/WORLD.md.
Types, composition and promotion
A request that matches a type or one of its familiar names uses that type.
When none fits, compose: pick the pattern by the reader's question
(skills/writing-documents/references/type-index.md), use only the modules the
registry in core/document-patterns.md allows for that pattern, and borrow the
nearest type's section discipline (references/composing.md). Do not force the
nearest preset, and do not add a type for a one-off request. A composed shape
seen three times is promoted to a type; that is the only way the catalog grows.
The catalog is edited in one place. A type's slug, aliases, pattern and
default-theme live only in its type-<slug>.md yaml block, and the
families table in core/document-patterns.md lists it. scripts/catalog.py
derives everything else — the build, the Patterns page, the site, the
validator and the tests — from those files, the module registry, the
reader-question table in type-index.md and the stages in
consultancy-lifecycle.md. Gallery card copy lives in TYPE_QUESTIONS and
COMPOSED_GALLERY in scripts/build_examples.py; the homepage story lives in
STORY in scripts/build_site.py, with every date taken from the example it
links to.
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.
- 9d ago Changed · +64 lines · +652 tokens per session d9f99cbb5875
- 26d ago Changed · +10 lines · +117 tokens per session 90a8bf05265a
- 1mo ago First seen · 37 lines · 347 tokens per session scan A d1bb68cd6800
document-design-system AGENTS.md is an instructions file published in the GitHub repository Avinava/document-design-system (2 stars, last pushed 10d ago), licensed MIT. It adds 1,116 tokens to every session, about $0.0045 per session on Opus 5.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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).