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 skills/zircote-plugins/adr/adr-format-madrnpx skills add zircote-plugins/adr --skill adr-format-madrgit clone --depth 1 https://github.com/zircote-plugins/adrWrote 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/skills/zircote-plugins/adr/adr-format-madr)<a href="https://agentmods.dev/skills/zircote-plugins/adr/adr-format-madr"><img src="https://agentmods.dev/badge/skills/zircote-plugins/adr/adr-format-madr.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.00063 | $0.01499 |
| Opus 5 | $0.00032 | $0.00749 |
| Sonnet 5 | $0.00013 | $0.00300 |
| Haiku 4.5 | $0.00006 | $0.00150 |
Grade A, and why
adr-format-madr 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 5d 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MADR Format
MADR (Markdown Architectural Decision Records) is a lean, developer-friendly ADR format that emphasizes considered options and their pros/cons. It is the default format for the ADR plugin.
About MADR
MADR is:
- Lean - Focuses on essential decision documentation
- Markdown-native - Designed for version control
- Option-focused - Emphasizes alternatives considered
- Flexible - Offers full and minimal variants
Current version: MADR 4.0.0
Template Variants
Full Template
All sections including optional ones. Use for important decisions requiring comprehensive documentation.
Sections:
- Title (H1)
- Status
- Context and Problem Statement
- Decision Drivers
- Considered Options
- Decision Outcome
- Consequences (Good/Bad)
- Confirmation
- Pros and Cons of the Options
- More Information
Minimal Template
Only mandatory sections. Use for simpler decisions or when brevity is preferred.
Sections:
- Title (H1)
- Status
- Context and Problem Statement
- Decision Outcome
Bare Templates
Same sections as full/minimal but without explanatory text. For experienced teams who know the format.
Section Guide
Title (Required)
Format: # {Short Title}
The title should:
- Be a short noun phrase
- Describe the decision topic
- Use title case
Examples:
# Use PostgreSQL for Primary Storage# Adopt Event-Driven Architecture
Status (Required)
The current status of the decision.
Valid values: proposed, accepted, deprecated, superseded
Include metadata if needed:
## Status
Accepted
Supersedes ADR-0003
Context and Problem Statement (Required)
Describe the context and the problem requiring a decision.
Format options:
- Free-form prose (2-3 sentences)
- Illustrative story
- Question format
Example:
## Context and Problem Statement
Our order processing system experiences high latency during peak hours.
We need to decouple order submission from order processing to improve
responsiveness. The current synchronous architecture cannot scale to
meet projected growth of 5x order volume.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 285 lines · 63 tokens per session scan A 2a9c9cef2027
adr-format-madr is a skill published in the GitHub repository zircote-plugins/adr (5 stars, last pushed 18d ago), licensed MIT. It adds 63 tokens to every session and 1,499 once invoked, about $0.0003 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 skills, from other repositories
bootstrap
Scaffold or retrofit documentation-led conventions (AGENTS.md, CLAUDE.md, CONVENTIONS.md, ADR catalogue, plan/ queue, agent/ coordination) into a repo. Use when the user asks to "set up conventions", "bootstrap ADRs", "scaffold the documentation-led layout", "add AGENTS.md and a plan queue", or invokes /bootstrap.…
audit
Audit a documentation-led repo against its own conventions — contiguous ADR numbering, INDEX sync, plan/ coverage, required sections, status validity, cross-reference resolution, language mandate, ADR-privacy leaks into user-visible code, cross-worktree collisions (duplicate numbers, duplicate plan ownership, same ADR…
agent-wave
Orchestrate a wave of parallel agents over the plan/todo queue in a documentation-led repo — asks how many agents, the budget (items/waves, with hours as a soft cap), and whether to checkpoint after each wave or run continuously. Spawns isolated worktree subagents, assigns one queue item each, collects results. Use…
new-adr
Author a new ADR — record a DECISION (what the system must do, or how it is built) in a documentation-led repo. Picks the next contiguous number, chooses the shape (capability vs technology), fills the template, sets status Proposed, regenerates INDEX, updates domain READMEs, handles supersede/deprecate linkage…
add-convention
Assess and add a CONVENTION (a reusable rule, practice, or naming/process standard) to a documentation-led repo — decides FIRST whether it is worth codifying at all, then routes it to the right home (AGENTS.md hard rule, CONVENTIONS.md guidance, GLOSSARY term, or to /new-adr if it is really a one-off decision). Pushes…
new-plan
Queue a UNIT OF WORK in the plan/todo queue of a documentation-led repo, tracing to an existing ADR — names the owning ADR(s), scope, exit criteria mapped to acceptance criteria, dependencies, and queue position. Use when the user says "add a plan item", "queue this work", "create a todo for ADR X", "new plan", "put…