A command for changing an existing Architectural Decision Record, a document that records a technical choice, its status, or its supporting details.

Use it to accept, reject, deprecate, or supersede a record, or add decision drivers and consequences.

It avoids manually locating and editing records when a decision changes.

adr-update — Command by zircote-plugins

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/zircote-plugins/adr/adr-update

Clone the repo

git clone --depth 1 https://github.com/zircote-plugins/adr

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 583 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.

Model	Per session	Once invoked
Fable 5	$0.00015	$0.00583
Opus 5	$0.00008	$0.00292
Sonnet 5	$0.00003	$0.00117
Haiku 4.5	$0.00002	$0.00058

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

Security

Grade A, and why

adr-update 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-update.md · 107 lines

How it starts

The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Update ADR

Update an existing Architectural Decision Record's status, content, or metadata.

Process

Parse arguments to identify ADR and update type
Find ADR file by ID
Read current content
Apply updates based on arguments
Update index if needed
Git commit if configured

Argument Parsing

Supported arguments:

<adr-id>: ADR number (e.g., "0001", "1", "ADR-0001")
--status=<status>: Update status (accepted, rejected, deprecated, superseded)
--add-driver=<driver>: Add a decision driver
--add-consequence=<consequence>: Add a consequence
No status flag: Open interactive update mode

ADR Resolution

Find ADR by flexible matching:

"1" → finds 0001-*.md
"0001" → finds 0001-*.md
"ADR-0001" → finds 0001-*.md
"use-postgresql" → finds use-postgresql.md

Status Update

When updating status:

To "accepted"

Update Status section
Add acceptance date if not present
Optionally add decision makers

To "rejected"

Update Status section
Prompt for rejection reason
Add rejection date

To "deprecated"

Update Status section
Prompt for deprecation reason
Suggest creating successor ADR

To "superseded"

Require superseding ADR ID
Update Status section
Add "Superseded by ADR-XXXX"
Update superseding ADR with "Supersedes ADR-YYYY"

Content Updates

For interactive updates, use AskUserQuestion:

What section to update?
What is the new content?
Any additional changes?

Index Update

After status change:

Read README.md index
Update status in ADR table
Write updated README.md

Git Integration

If git integration enabled:

git add {adr_file}
git commit -m "docs(adr): update ADR-{id} status to {status}"

Output

Report changes made:

Previous status → New status
Sections modified
Related ADRs updated
Git commit created (if applicable)

Validation

Before updating:

Verify ADR exists
Validate status transition is allowed
Check for missing required fields

Read the full file on GitHub · 107 lines

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.

yesterday First seen · 107 lines · 15 tokens per session scan A 539d5249e1a5

Subscribe to this mod's changes

adr-update is a command published in the GitHub repository zircote-plugins/adr (5 stars, last pushed 14d ago), licensed MIT. It adds 15 tokens to every session and 583 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.

Documents Planning Writing and docs adr architecture-decision-records claude-code claude-code-plugin documentation madr

adr-update