Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add zircote-plugins/adr/plugin install 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-format-tyree-akerman)<a href="https://agentmods.dev/skills/zircote-plugins/adr/adr-format-tyree-akerman"><img src="https://agentmods.dev/badge/skills/zircote-plugins/adr/adr-format-tyree-akerman.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.00067 | $0.01042 |
| Opus 5 | $0.00034 | $0.00521 |
| Sonnet 5 | $0.00013 | $0.00208 |
| Haiku 4.5 | $0.00007 | $0.00104 |
Grade A, and why
adr-format-tyree-akerman 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 5d 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tyree-Akerman ADR Format
The Tyree-Akerman format, developed by Jeff Tyree and Art Akerman, is a comprehensive template for enterprise-grade architectural decision documentation. It provides extensive traceability to requirements, principles, and related artifacts.
About Tyree-Akerman Format
The Tyree-Akerman format is:
- Comprehensive - Covers all aspects of decision documentation
- Traceable - Links to requirements, principles, artifacts
- Enterprise-ready - Supports formal governance
- RACI-aware - Documents decision makers and stakeholders
Template Structure
# {NUMBER}. {TITLE}
## Metadata
| Attribute | Value |
|-----------|-------|
| Status | {STATUS} |
| Date | {DATE} |
| Decision Makers | {names/roles} |
| Consulted | {names/roles} |
| Informed | {names/roles} |
## Issue
{Architectural question}
## Decision
{Clear decision statement}
## Assumptions
* {Assumption 1}
* {Assumption 2}
## Constraints
* {Constraint 1}
* {Constraint 2}
## Positions
### Position 1: {Title}
{Analysis}
### Position 2: {Title}
{Analysis}
## Argument
{Reasoning for decision}
## Implications
* {Implication 1}
* {Implication 2}
## Related Decisions
## Related Requirements
## Related Artifacts
## Related Principles
## Notes
Section Guide
Metadata Table
Document decision governance:
| Field | Purpose |
|---|---|
| Status | Current decision state |
| Date | Decision date |
| Decision Makers | Those with final authority |
| Consulted | Those providing input |
| Informed | Those who need to know |
Issue
State the architectural question clearly:
- What needs to be decided?
- Be precise and unambiguous
- Focus on the architectural aspect
Decision
State the decision clearly:
- Unambiguous statement
- Specific enough to act upon
- Direct language
Assumptions
List underlying assumptions:
- What is assumed to be true
- Conditions the decision depends on
- Beliefs about the future
What ships with it
2 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.
- 5d ago First seen · 217 lines · 67 tokens per session scan A 92e02a66806b
adr-format-tyree-akerman is a skill published in the GitHub repository zircote-plugins/adr (5 stars, last pushed 19d ago), licensed MIT. It adds 67 tokens to every session and 1,042 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…