adr

A command for creating and maintaining Architecture Decision Records, or short documents that explain important technical choices and their rejected alternatives. It also connects those decisions to agent instructions for future sessions.

In plain words
What is it for?
Useful for installing an ADR folder and index, writing decision records, listing decisions that need backfilling, and guiding agents around accepted architecture choices.
Why use it?
It preserves the reasoning behind architecture choices so later work does not silently contradict them. It keeps decision history separate from handoff notes and documentation-sync work.

Command

Install

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.

agentmods
npx agentmods add commands/kensaurus/cursor-kenji/adr
Clone the repo
git clone --depth 1 https://github.com/kensaurus/cursor-kenji
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 132 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00011 $0.00132
Opus 5 $0.00005 $0.00066
Sonnet 5 $0.00002 $0.00026
Haiku 4.5 $0.00001 $0.00013

Measured yesterday against content hash 9811a80a3543, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

commands/adr.md · 17 lines

What it actually says

Architecture Decision Records

Run the docs-adr skill: install docs/adr/ + INDEX.md, write one-page records with a Rejected alternatives section, and wire agent rules so a future session cannot silently contradict an Accepted ADR.

Docs-vs-code drift stays on plan-docs-sync. Session state stays on /handoff. Present the backfill list before writing ADRs.

The full playbook lives in the docs-adr skill.

Changes

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.

  1. yesterday First seen · 17 lines · 11 tokens per session scan A 9811a80a3543

Subscribe to this mod's changes

adr is a command published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 3d ago), licensed MIT. It adds 11 tokens to every session and 132 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.