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/rvdbreemen/adr-kit/adrnpx skills add rvdbreemen/adr-kit --skill adrgit clone --depth 1 https://github.com/rvdbreemen/adr-kitWrote 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/rvdbreemen/adr-kit/adr)<a href="https://agentmods.dev/skills/rvdbreemen/adr-kit/adr"><img src="https://agentmods.dev/badge/skills/rvdbreemen/adr-kit/adr.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.1 | $0.00019 | $0.00312 |
| Opus 5 | $0.00010 | $0.00156 |
| Sonnet 5 | $0.00004 | $0.00062 |
| Haiku 4.5 | $0.00002 | $0.00031 |
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 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.
What it actually says
ADR authoring
Invoke explicitly with $adr-kit:adr when needed.
Resolve <plugin-root> from this installed skill. Use only bundled,
local ADR Kit tools and follow this canonical workflow:
- Query the generated ADR index for relevant Accepted ADRs before writing, open only returned sources, and report conflicts.
- Run
python <plugin-root>/bin/adr profiles --format json; use only a returned profile withavailable: true. - Use
madras the default; supportnygardandcanonicalonly when returned as available, and never invent a profile or template. - Qualify
<subject>as a consequential, difficult-to-reverse decision before creating a record; do not create an ADR for an ordinary reversible implementation choice. - Create a Proposed record, then follow the canonical grill protocol for context, decision, alternatives, consequences, risks, mitigations, evidence, scope, ownership, conflicts, and Open Questions.
- Show the final acceptance packet and require an explicit
yesin this active session before invokingadr accept ... --confirm; require Completeness, Evidence, Clarity, and Consistency and supersede rather than rewriting Accepted decisions.
Do not contact another model or mutate user-owned instructions.
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 · 22 lines · 19 tokens per session scan A e8c68158e166
adr is a skill published in the GitHub repository rvdbreemen/adr-kit (6 stars, last pushed 9d ago), licensed MIT. It adds 19 tokens to every session and 312 once invoked, about $0.0001 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.…
decision-backfill
Use when auditing an existing codebase, documentation set, plans, RFCs, or git history for architecture decisions that were made but never recorded as ADRs, and when triaging potential records before drafting them.
decision-memory
Use when planning, designing, reviewing, or changing code in a repository that keeps ADRs (usually docs/adr) — to load the decisions that already govern the work, check a plan or diff against them, or record a new decision. Also use when a choice feels already-settled and you cannot find where it was settled.
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…
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…
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…