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 skills add rvdbreemen/adr-kit --skill relatedgit 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/related)<a href="https://agentmods.dev/skills/rvdbreemen/adr-kit/related"><img src="https://agentmods.dev/badge/skills/rvdbreemen/adr-kit/related/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/skills/rvdbreemen/adr-kit/related"><img src="https://agentmods.dev/badge/skills/rvdbreemen/adr-kit/related.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.00018 | $0.00165 |
| Opus 5.5 | $0.00007 | $0.00066 |
| Sonnet 5.5 | $0.00004 | $0.00033 |
| Haiku 4.5 | $0.00002 | $0.00016 |
Grade A, and why
related 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 11d 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 relationships
Reply in the language the user writes in; default to English. Keep command output, identifiers, paths, and ADR file content unchanged.
Invoke explicitly with $adr-kit:related when needed.
Resolve <plugin-root> from this installed skill. Use only bundled,
local ADR Kit tools and follow this canonical workflow:
- Run
adr-related <ADR-NNN> --adr-dir docs/adr --format jsonand report typed inbound, outbound, dangling, and ambiguous links.
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.
- 11d ago Changed · +2 lines 5523fab210e8
- 1mo ago First seen · 17 lines · 18 tokens per session scan A 5a7fdbea8d4a
related is a skill published in the GitHub repository rvdbreemen/adr-kit (13 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 165 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 skills, from other repositories
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.
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", or "add AGENTS.md and a plan queue". Works on fresh repos…
agent-wave
Run a bounded wave over the plan/todo queue in a documentation-led repo, using available parallel agents or sequential execution. Establishes width, budget and supervision; isolates work and collects verified outcomes. Use for "spawn a wave of agents", "run the queue in parallel", "fan out the work", or "agent wave"…
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…
actual
Feature-complete companion for the actual CLI, an ADR-powered CLAUDE.md/AGENTS.md generator. Runs and troubleshoots actual adr-bot, status, auth, config, runners, and models, plus the Actual AI platform surface: login, logout, whoami, and advisor (org-scoped architecture Q&A). Covers all 5 runners (claude-cli…