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-business-case)<a href="https://agentmods.dev/skills/zircote-plugins/adr/adr-format-business-case"><img src="https://agentmods.dev/badge/skills/zircote-plugins/adr/adr-format-business-case.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.00063 | $0.00873 |
| Opus 5 | $0.00032 | $0.00436 |
| Sonnet 5 | $0.00013 | $0.00175 |
| Haiku 4.5 | $0.00006 | $0.00087 |
Grade A, and why
adr-format-business-case 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business Case ADR Format
The Business Case format is designed for decisions requiring financial analysis, stakeholder sign-off, and executive-level documentation. It includes SWOT analysis, cost-benefit analysis, and ROI assessment.
About Business Case Format
The Business Case format is:
- Executive-focused - Clear for non-technical stakeholders
- Financial - Includes cost-benefit and ROI analysis
- Comprehensive - SWOT, risks, and implementation planning
- Formal - Stakeholder sign-off section
Template Structure
# {NUMBER}. {TITLE}
Date: {DATE}
## Status
{STATUS}
## Executive Summary
{2-3 sentence overview}
## Business Context
{Business situation description}
## Problem Statement
{Business problem or opportunity}
## SWOT Analysis
### Strengths
### Weaknesses
### Opportunities
### Threats
## Options Considered
### Option 1: {Title}
**Cost**: {Estimate}
**Effort**: {High/Medium/Low}
**Risk**: {High/Medium/Low}
**Alignment**: {Strategic alignment}
## Decision
{Chosen option and justification}
## Cost-Benefit Analysis
### Costs
### Benefits
### ROI Assessment
## Implementation
### Timeline
### Resources Required
### Success Metrics
## Risk Assessment
{Risk table with likelihood, impact, mitigation}
## Stakeholder Sign-off
{Sign-off table}
Section Guide
Executive Summary
Brief overview for executives:
- What decision was made
- Why it matters to the business
- Key financial impact
Business Context
Describe business situation:
- Market conditions
- Competitive pressures
- Customer needs
- Organizational goals
SWOT Analysis
| Category | Focus |
|---|---|
| Strengths | Internal positive factors |
| Weaknesses | Internal limitations |
| Opportunities | External potential gains |
| Threats | External risks |
Options with Business Metrics
For each option, document:
- Cost: Initial and ongoing
- Effort: Implementation effort
- Risk: Overall risk level
- Alignment: Fit with strategic goals
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.
- 6d ago First seen · 194 lines · 63 tokens per session scan A 45e293678d10
adr-format-business-case is a skill published in the GitHub repository zircote-plugins/adr (5 stars, last pushed 20d ago), licensed MIT. It adds 63 tokens to every session and 873 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.…
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…
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…
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…