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 instructions/rvdbreemen/adr-kit/agents-mdgit 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/instructions/rvdbreemen/adr-kit/agents-md)<a href="https://agentmods.dev/instructions/rvdbreemen/adr-kit/agents-md"><img src="https://agentmods.dev/badge/instructions/rvdbreemen/adr-kit/agents-md.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.00327 | $0.00327 |
| Opus 5 | $0.00163 | $0.00163 |
| Sonnet 5 | $0.00065 | $0.00065 |
| Haiku 4.5 | $0.00033 | $0.00033 |
Grade A, and why
adr-kit 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 4d 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-kit Agent Instructions
These instructions adapt the repository guidance for Codex and other coding
agents working in adr-kit.
Task management
- Treat Backlog.md as the source of truth for meaningful work.
- Search for an existing task before starting implementation work.
- If no task exists, create one before editing code or docs.
- Prefer the Backlog MCP tools for reading, searching, creating, and updating
tasks. Use the
backlogCLI only when MCP is unavailable or insufficient. - Do not edit files in
backlog/tasks/directly. - Keep tasks small enough to finish in one focused pass.
Repo conventions
- Keep changes small, focused, and dependency-free unless the roadmap says otherwise.
- Follow the existing adr-kit conventions in
README.md,ROADMAP.md, andCLAUDE.md. - Favor deterministic, stdlib-first changes over new runtime dependencies.
Verification
- Run the smallest test or check that proves the change.
- Broaden verification when the change touches shared behavior, tooling, package layout, or user-facing workflow.
- Before marking work done, make sure the task status and notes in Backlog are updated to match the actual change.
ADR Kit
Read .adr-kit/ADR-guide.md before architectural changes. Architecture decisions live in docs/adr/. Use $adr-kit:context before implementation, $adr-kit:adr for new decisions, and $adr-kit:judge before commit.
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.
- 4d ago First seen · 37 lines · 327 tokens per session scan A 81efc0f54e52
adr-kit AGENTS.md is an instructions file published in the GitHub repository rvdbreemen/adr-kit (5 stars, last pushed 7d ago), licensed MIT. It adds 327 tokens to every session, about $0.0016 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 instructions, from other repositories
adrkit AGENTS.md
Instructions for mbeacom/adrkit, covering adrkit, visual adr graph, inbound @adr markers (v0.5.0: explain, check, and ci), the spec kit extension (packages/adapters/spec-kit) and adr queue.
codebase-intel CLAUDE.md
Instructions for MutharasuArchunan13/codebase-intel, covering codebase intel — project claude.md, project overview, tech stack, architecture and module responsibilities.
adrkit copilot-instructions.md
Instructions for mbeacom/adrkit, covering adrkit — github copilot and github copilot specifics.
adrkit CLAUDE.md
Instructions for mbeacom/adrkit, covering adrkit — claude code and claude code specifics.
adr copilot-instructions.md
Instructions for zircote-plugins/adr, covering copilot instructions, project overview, key components, plugin structure and development guidelines.
docflow AGENTS.md
Instructions for EvolveHQ/docflow, covering agents.md, what this repository is, repository structure, hard rules when editing adrs and domain-specific hard rules.