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.
git 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/commands/avinava/document-design-system/adr)<a href="https://agentmods.dev/commands/avinava/document-design-system/adr"><img src="https://agentmods.dev/badge/commands/avinava/document-design-system/adr/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/commands/avinava/document-design-system/adr"><img src="https://agentmods.dev/badge/commands/avinava/document-design-system/adr.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.00032 | $0.00134 |
| Opus 5.5 | $0.00013 | $0.00054 |
| Sonnet 5.5 | $0.00006 | $0.00027 |
| Haiku 4.5 | $0.00003 | $0.00013 |
Grade A, and why
adr 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 1mo 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- runbook — 88% identical, 6 lines differ
- architecture — 86% identical, 6 lines differ
- spec — 86% identical, 6 lines differ
- discovery — 86% identical, 6 lines differ
- design-handoff — 86% identical, 6 lines differ
- explanation — 86% identical, 6 lines differ
- handoff — 84% identical, 6 lines differ
- postmortem — 84% identical, 6 lines differ
What it actually says
Use the writing-documents skill.
Type slug: adr
Load references/type-adr.md, references/writing.md, references/evidence.md.
Default output is Markdown in the user's project at this type's conventional path.
Do not assemble HTML, pick a theme, inline CSS, or run build_document.py unless
the user asked for HTML, PDF, print, or designed output.
If they did, also load references/output.md and core/.
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.
- 1mo ago First seen · 12 lines · 32 tokens per session scan A d111ee98a2df
adr is a command published in the GitHub repository Avinava/document-design-system (2 stars, last pushed 10d ago), licensed MIT. It adds 32 tokens to every session and 134 once invoked, about $0.0001 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 commands, from other repositories
pr
Take the current branch from uncommitted work to an open pull request: commit outstanding changes with the git-commit rules if asked, push with upstream tracking, write the PR title and body with the pr-description skill from the full branch diff, link the issue, and open it with gh against the right base. Confirms…
evaluate
Execute Evaluate stage to validate generated framework artifacts.
design-review
Run the 7-phase design review (WCAG AA, responsive, interaction) on a page or URL.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.