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/madappgang/claude-code/adr-documentationnpx skills add MadAppGang/claude-code --skill adr-documentationgit clone --depth 1 https://github.com/MadAppGang/claude-codeWrote 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/madappgang/claude-code/adr-documentation)<a href="https://agentmods.dev/skills/madappgang/claude-code/adr-documentation"><img src="https://agentmods.dev/badge/skills/madappgang/claude-code/adr-documentation.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.00060 | $0.05752 |
| Opus 5 | $0.00030 | $0.02876 |
| Sonnet 5 | $0.00012 | $0.01150 |
| Haiku 4.5 | $0.00006 | $0.00575 |
Grade A, and why
adr-documentation 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 2d 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 — 930 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ADR Documentation
Overview
What are ADRs?
Architecture Decision Records (ADRs) are lightweight documents that capture important architectural decisions along with their context and consequences. They serve as a historical record of why certain choices were made, helping teams avoid revisiting settled debates and providing context for future developers.
Key characteristics:
- Immutable: Once accepted, ADRs are rarely modified (supersede instead)
- Context-rich: Capture the environment and constraints at decision time
- Outcome-focused: Document what was decided and why
- Alternative-aware: Show what options were considered and rejected
Why Document Decisions?
Context Preservation:
- Future team members understand why things are the way they are
- Avoid "we've always done it this way" without knowing the reason
- Preserve institutional knowledge across team changes
Onboarding:
- New developers can read ADR history to understand system evolution
- Reduces repetitive explanations of architectural choices
- Provides learning path through project decisions
Avoiding Repeat Mistakes:
- Document why certain approaches were rejected
- Prevent re-proposing failed solutions
- Learn from past trade-offs
Alignment:
- Create shared understanding across team
- Resolve disagreements with documented rationale
- Enable asynchronous decision-making
When to Write an ADR
Write an ADR when:
- Significant architectural choices: Microservices vs monolith, event-driven vs request/response
- Technology selections: Database choice, framework adoption, language decisions
- Pattern decisions: State management approach, authentication strategy, error handling patterns
- Breaking changes: API redesigns, data model changes, migration strategies
- Performance-critical decisions: Caching strategies, optimization approaches, scalability patterns
- Security-related choices: Authentication methods, encryption strategies, access control models
- Infrastructure decisions: Deployment strategy, hosting platform, CI/CD approach
- Dependency selections: Major library choices, third-party service integrations
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.
- 2d ago First seen · 930 lines · 60 tokens per session scan A fa624eb407ee
adr-documentation is a skill published in the GitHub repository MadAppGang/claude-code (279 stars, last pushed 5mo ago), licensed MIT. It adds 60 tokens to every session and 5,752 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-09-03.
Other skills, from other repositories
adr-writing
Write Architecture Decision Records future engineers will actually read. Invoke when making a non-trivial architectural choice that you want to defend later.
architecture-decision-record-creator
Create structured Architecture Decision Records (ADRs) with 7 sections to document architecture decisions with full justification. Use this skill whenever the user has made or needs to make an architecture decision, wants to document why a technical choice was made, is choosing between technologies or patterns, needs…
architecture-decision-records
Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.
open-change
Open a durable record in the change plane (decisions/) for a unit of work or an architecture decision, with its context, the choice, and the alternatives weighed.
system-design-patterns
Architecture patterns (monolith, microservices, CQRS, event-driven, api-gateway, scalability), ADR methodology, trade-off analysis, fitness functions, and deterministic ADR completeness scoring via executable script. Use proactively when making or reviewing significant architectural decisions, writing or auditing…
write-adr
Creates an Architecture Decision Record (ADR) documenting a significant technical decision. Follows the standard ADR format with context, decision, and consequences. Invoked when the user says "write an ADR", "document this decision", or "create an architecture record".