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 commands/zircote-plugins/adr/adr-supersedegit clone --depth 1 https://github.com/zircote-plugins/adrWrote 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/commands/zircote-plugins/adr/adr-supersede)<a href="https://agentmods.dev/commands/zircote-plugins/adr/adr-supersede"><img src="https://agentmods.dev/badge/commands/zircote-plugins/adr/adr-supersede.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.00016 | $0.00820 |
| Opus 5 | $0.00008 | $0.00410 |
| Sonnet 5 | $0.00003 | $0.00164 |
| Haiku 4.5 | $0.00002 | $0.00082 |
Grade A, and why
adr-supersede 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Supersede ADR
Create a new ADR that supersedes an existing one, with proper bidirectional linking.
Process
- Parse arguments to get existing ADR ID and new title
- Verify existing ADR exists and is supersedable
- Gather supersession context (why superseding)
- Create new ADR with "Supersedes ADR-XXXX"
- Update old ADR status to "superseded" with "Superseded by ADR-YYYY"
- Update index with both changes
- Git commit if configured
Argument Parsing
Required arguments:
<existing-adr-id>: The ADR being superseded<new-title>: Title for the new ADR
Pre-Supersession Checks
Verify the existing ADR:
- Exists
- Is in "accepted" or "deprecated" status
- Is not already superseded
If already superseded, warn and suggest:
- Supersede the current successor instead
- Or proceed with supersession chain
Context Gathering
Ask for supersession context:
- Reason: "Why is the original ADR being superseded?"
- Changes: "What key changes does the new decision make?"
- Migration: "Is there a migration path from old to new?"
New ADR Creation
Create new ADR with:
- Next sequential number
- User-provided title
- Status: "proposed" (or "accepted" if immediate)
- Supersedes section linking to old ADR
- Context includes reference to superseded decision
Template addition:
## Status
Proposed
Supersedes [ADR-{old_id}](./0001-old-title.md)
## Context and Problem Statement
This decision supersedes ADR-{old_id} because {reason}.
{Additional context}
Old ADR Update
Update the superseded ADR:
## Status
Superseded by [ADR-{new_id}](./0002-new-title.md)
**Note**: This ADR has been superseded. See ADR-{new_id} for the current decision.
Index Update
Update README.md:
- Add new ADR entry
- Update old ADR status to "superseded"
- Add supersession relationship in "Related" column if present
Supersession Chain
If superseding an ADR that itself superseded another:
- Document full chain in new ADR
- Update "More Information" section with history
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.
- 3d ago First seen · 137 lines · 16 tokens per session scan A 273ae4c8701c
adr-supersede is a command published in the GitHub repository zircote-plugins/adr (5 stars, last pushed 17d ago), licensed MIT. It adds 16 tokens to every session and 820 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 commands, from other repositories
feature-plan
Guide the agent to create or update a feature plan from a short feature request.
adr-check
Check the current change, or a plan, against the decisions that govern it and report a verdict per decision. Read-only.
check
Check a produced plan against the decisions that govern it. Read-only.
draft
Draft one new ADR from the current plan artifact. Writes a single new record.
context
Retrieve the decisions that govern this work into context, before planning against them. Read-only.
documentation-generator
Generate comprehensive documentation for code and APIs.