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 skills/zircote-plugins/adr/adr-fundamentalsnpx skills add zircote-plugins/adr --skill adr-fundamentalsgit 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/skills/zircote-plugins/adr/adr-fundamentals)<a href="https://agentmods.dev/skills/zircote-plugins/adr/adr-fundamentals"><img src="https://agentmods.dev/badge/skills/zircote-plugins/adr/adr-fundamentals.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.1 | $0.00068 | $0.01511 |
| Opus 5 | $0.00034 | $0.00756 |
| Sonnet 5 | $0.00014 | $0.00302 |
| Haiku 4.5 | $0.00007 | $0.00151 |
Grade A, and why
adr-fundamentals 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 6d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ADR Fundamentals
Architectural Decision Records (ADRs) capture important architectural decisions along with their context and consequences. This skill provides foundational knowledge for creating, managing, and maintaining ADRs effectively.
When to Create an ADR
Create an ADR when making decisions that:
- Have significant impact - Affect system structure, behavior, or quality attributes
- Are hard to reverse - Would require substantial effort to change later
- Have multiple viable options - Alternatives were seriously considered
- Affect multiple components - Cross-cutting concerns or system-wide patterns
- Set precedent - Establish patterns others will follow
- Involve trade-offs - Balance competing concerns or constraints
Common ADR-Worthy Decisions
| Category | Examples |
|---|---|
| Technology Selection | Programming language, framework, database, cloud provider |
| Architecture Patterns | Microservices vs monolith, event-driven, CQRS |
| API Design | REST vs GraphQL, versioning strategy, authentication |
| Data Management | Storage strategy, caching, replication, backup |
| Security | Authentication method, encryption, access control |
| Integration | Third-party services, messaging patterns, protocols |
| Infrastructure | Container orchestration, deployment strategy, scaling |
When NOT to Create an ADR
Skip ADRs for:
- Routine implementation choices
- Decisions with obvious answers
- Temporary or experimental changes
- Minor configuration tweaks
- Decisions that can be easily reversed
ADR Lifecycle
Status Workflow
proposed → accepted → [deprecated] → superseded
↓
rejected
| Status | Meaning |
|---|---|
| proposed | Under consideration, open for discussion |
| accepted | Approved and active, guides current development |
| rejected | Considered but not adopted (document why) |
| deprecated | No longer recommended, pending replacement |
| superseded | Replaced by a newer ADR (link to successor) |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 221 lines · 68 tokens per session scan A 3f7a8ea771bd
adr-fundamentals is a skill published in the GitHub repository zircote-plugins/adr (5 stars, last pushed 19d ago), licensed MIT. It adds 68 tokens to every session and 1,511 once invoked, about $0.0003 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 skills, from other repositories
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", "add AGENTS.md and a plan queue", or invokes /bootstrap.…
agent-wave
Orchestrate a wave of parallel agents over the plan/todo queue in a documentation-led repo — asks how many agents, the budget (items/waves, with hours as a soft cap), and whether to checkpoint after each wave or run continuously. Spawns isolated worktree subagents, assigns one queue item each, collects results. Use…
audit
Audit a documentation-led repo against its own conventions — contiguous ADR numbering, INDEX sync, plan/ coverage, required sections, status validity, cross-reference resolution, language mandate, ADR-privacy leaks into user-visible code, cross-worktree collisions (duplicate numbers, duplicate plan ownership, same ADR…
new-adr
Author a new ADR — record a DECISION (what the system must do, or how it is built) in a documentation-led repo. Picks the next contiguous number, chooses the shape (capability vs technology), fills the template, sets status Proposed, regenerates INDEX, updates domain READMEs, handles supersede/deprecate linkage…
add-convention
Assess and add a CONVENTION (a reusable rule, practice, or naming/process standard) to a documentation-led repo — decides FIRST whether it is worth codifying at all, then routes it to the right home (AGENTS.md hard rule, CONVENTIONS.md guidance, GLOSSARY term, or to /new-adr if it is really a one-off decision). Pushes…
brainstorm
Decompose a problem, feature, or goal into candidate ADRs and plan items for a documentation-led repo — one decision per ADR, dependency edges, suggested ordering. Proposes drafts for review and writes nothing until approved. Use when the user says "brainstorm ADRs", "break this down into decisions", "what ADRs do we…