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 intent-driven-dev/intent-driven-template --skill architectural-decision-recordsgit clone --depth 1 https://github.com/intent-driven-dev/intent-driven-templateWrote 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/intent-driven-dev/intent-driven-template/architectural-decision-records)<a href="https://agentmods.dev/skills/intent-driven-dev/intent-driven-template/architectural-decision-records"><img src="https://agentmods.dev/badge/skills/intent-driven-dev/intent-driven-template/architectural-decision-records/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/intent-driven-dev/intent-driven-template/architectural-decision-records"><img src="https://agentmods.dev/badge/skills/intent-driven-dev/intent-driven-template/architectural-decision-records.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00040 | $0.00865 |
| Opus 5.5 | $0.00016 | $0.00346 |
| Sonnet 5.5 | $0.00008 | $0.00173 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
architectural-decision-records 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 1mo 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architectural Decision Records
Overview
An Architectural Decision Record captures one architecturally significant decision, its rationale, tradeoffs, and consequences. Optimize for future readers reconstructing decision history.
When to Use
Use when creating, updating, reviewing, or explaining an ADR, architecture decision, decision log, tradeoff analysis, rationale, consequences, alternatives, or status.
Do not use ADRs for transient implementation details, meeting notes, or insignificant decisions. If significance is unclear, ask what future maintainers will need to know.
Workflow
- Identify the single decision. Split multiple decisions into multiple ADRs.
- Check
preferences.mdforpreferred-style. - If
preferred-style: unset, ask the user which style to use, then record it inpreferences.mdbefore drafting. - Use the matching file under
templates/. - Capture known facts only: context, requirements, constraints, options, rationale, decision makers, consequences.
- If facts are missing, mark them as
Unknownor ask a focused question; do not invent context, options, or quality attributes. - Write honest consequences: benefits, downsides, follow-up.
- Preserve history: supersede old accepted ADRs; do not rewrite them away.
Template Choice
| Situation | Template |
|---|---|
| Detailed tradeoff record | templates/madr-full.md |
| Concise tradeoff record | templates/madr-minimal.md |
| Classic lightweight ADR | templates/nygard.md |
| One-sentence summary | templates/y-statement.md |
| Project-specific style | templates/custom.md |
| Too little evidence | ADR review notes/questions, not accepted ADR |
Status Values
| Status | Use when |
|---|---|
| Proposed | Under review |
| Accepted | Team committed |
| Deprecated | Historically relevant but no longer recommended |
| Superseded | Replaced by another ADR; link it |
Preference Prompt
If no preference is recorded, ask:
Which ADR style should I use and remember for this project: MADR full, MADR minimal, Nygard, Y-Statement, or custom?
What ships with it
6 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.
- 1mo ago First seen · 111 lines · 40 tokens per session scan A 7b1cae1dc52e
architectural-decision-records is a skill published in the GitHub repository intent-driven-dev/intent-driven-template (181 stars, last pushed 9d ago), licensed MIT. It adds 40 tokens to every session and 865 once invoked, about $0.0002 per session on Opus 5.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
build-executor
Execute an active direct request or approved planned change. Native continuous implementation is the default; existing legacy changes retain their recorded contract obligations.
bug-investigator
Use when encountering any bug, test failure, or unexpected behavior during spec-superflow execution, before proposing fixes. Invoked automatically when build-executor hits a blockage.
contract-builder
Maintain an execution contract only for an existing legacy change that requires one. New direct/planned changes do not invoke this skill when a contract is absent.
need-explorer
Clarify intent, scope, constraints, and success criteria before artifact creation. Invoke when the request is fuzzy, the user is comparing options, or the workflow needs a stable change definition before writing artifacts.
seats-aero
Search award flight availability across 27 mileage programs via Seats.aero Partner API. Find cheapest award flights, compare programs, and get booking links.
scandinavia-transit
Search trains, buses, and ferries in Norway (Entur), Sweden (ResRobot), and Denmark (Rejseplanen). Intra-Scandinavia ground transport with schedules and Danish fare pricing.