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 skills add sethdford/claude-skills --skill architecture-decision-recordgit clone --depth 1 https://github.com/sethdford/claude-skillsWrote 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/sethdford/claude-skills/architecture-decision-record)<a href="https://agentmods.dev/skills/sethdford/claude-skills/architecture-decision-record"><img src="https://agentmods.dev/badge/skills/sethdford/claude-skills/architecture-decision-record/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/sethdford/claude-skills/architecture-decision-record"><img src="https://agentmods.dev/badge/skills/sethdford/claude-skills/architecture-decision-record.svg" alt="Reviewed on agentmods" width="80" 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.00023 | $0.00343 |
| Opus 5 | $0.00012 | $0.00171 |
| Sonnet 5 | $0.00005 | $0.00069 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
architecture-decision-record 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 11d 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.
What it actually says
Architecture Decision Record
Document architectural decisions with context, rationale, and trade-offs using the ADR format for organizational memory.
Context
You are documenting an architectural decision. Use ADRs to capture decision rationale and ensure future teams understand why choices were made.
Domain Context
Based on Michael Nygard's ADR format and decision documentation best practices:
- Status: Proposed, Accepted, Superseded
- Context: Problem statement and constraints
- Decision: What was chosen and why
- Consequences: Benefits and drawbacks
Instructions
- Describe Problem: What decision needed to be made? What constraints?
- List Options: What alternatives were considered?
- Explain Rationale: Why was this option chosen? What trade-offs?
- Document Consequences: What problems does this solve? What new problems does it create?
- Link Related Decisions: ADRs supersede, depend on, or relate to other ADRs.
Anti-Patterns
- ADR Without Context: Decision seems arbitrary. Guard: Every ADR explains problem and constraints.
- Only Documenting Wins: Never documenting failures or reversals. Guard: Include failures and "Superseded" records.
- ADR Too Late: Decision made and implemented before documenting. Guard: Write ADR before implementation.
Further Reading
- Documenting Architecture Decisions by Michael Nygard
- ADR Repository at adr.github.io
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.
- 11d ago First seen · 41 lines · 23 tokens per session scan A 57925e8260c0
architecture-decision-record is a skill published in the GitHub repository sethdford/claude-skills (40 stars, last pushed 6mo ago), licensed MIT. It adds 23 tokens to every session and 343 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-30.
Other skills, from other repositories
videodb
See, Understand, Act on video and audio. See- ingest from local files, URLs, RTSP/live feeds, or live record desktop; return realtime context and playable stream links. Understand- extract frames, build visual/semantic/temporal indexes, and search moments with timestamps and auto-clips. Act- transcode and normalize…
lead-intelligence
AI-native lead intelligence and outreach pipeline. Replaces Apollo, Clay, and ZoomInfo with agent-powered signal scoring, mutual ranking, warm path discovery, and personalized outreach. Use when the user wants to find, qualify, and reach high-value contacts.
team-builder
Interactive agent picker for composing and dispatching parallel teams.
cmd_aside
Answer a quick side question without interrupting or losing context from the current task. Resume work automatically after answering.
springboot-verification
Verification loop for Spring Boot projects: build, static analysis, tests with coverage, security scans, and diff review before release or PR.
cmd_evolve
Cluster MEMORY.md entries by theme and optionally generate SKILL.md drafts.