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 commands/fomo-driven-development/strategic-claude-base/adr.templategit clone --depth 1 https://github.com/Fomo-Driven-Development/strategic-claude-baseWrote 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/commands/fomo-driven-development/strategic-claude-base/adr.template)<a href="https://agentmods.dev/commands/fomo-driven-development/strategic-claude-base/adr.template"><img src="https://agentmods.dev/badge/commands/fomo-driven-development/strategic-claude-base/adr.template.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.00000 | $0.00889 |
| Opus 5 | $0.00000 | $0.00445 |
| Sonnet 5 | $0.00000 | $0.00178 |
| Haiku 4.5 | $0.00000 | $0.00089 |
Grade A, and why
adr.template 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 4d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ADR-NNNN: [Decision Title]
Date: [Current date and time with timezone in ISO format] Git Commit: [Current commit hash] Branch: [Current branch name] Repository: [Repository name] Status: [proposed|accepted|rejected|deprecated|superseded]
Status
[Current status of this decision: proposed, accepted, rejected, deprecated, or superseded]
[If superseded, reference the superseding ADR: "Superseded by ADR-XXXX"] [If superseding, reference previous ADRs: "Supersedes ADR-XXXX, ADR-YYYY"]
Context
[What is the issue that we're seeing that is motivating this decision or change? Include:]
- Problem statement
- Current situation
- Business/technical drivers
- Constraints and requirements
- Stakeholders involved
Background
[Additional context about the domain, system, or environment where this decision applies]
Decision Drivers
- [Key factor 1 influencing this decision]
- [Key factor 2 influencing this decision]
- [Key factor 3 influencing this decision]
Decision
[What is the change that we're proposing and/or doing?]
[Clear statement of the architectural decision made]
Rationale
[Why this decision was made over alternatives]
Implementation Approach
[High-level approach for implementing this decision]
Consequences
[What becomes easier or more difficult to do because of this change?]
Positive Consequences
- [Benefit 1]
- [Benefit 2]
- [Benefit 3]
Negative Consequences
- [Trade-off 1]
- [Trade-off 2]
- [Trade-off 3]
Risks and Mitigation
- Risk: [Potential risk]
- Mitigation: [How to address this risk]
Alternatives Considered
Option 1: [Alternative name]
- Description: [Brief description]
- Pros: [Advantages]
- Cons: [Disadvantages]
- Rejected because: [Reason for rejection]
Option 2: [Alternative name]
- Description: [Brief description]
- Pros: [Advantages]
- Cons: [Disadvantages]
- Rejected because: [Reason for rejection]
Implementation Details
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.
- 4d ago First seen · 161 lines · 0 tokens per session scan A da933d70cdaf
adr.template is a command published in the GitHub repository Fomo-Driven-Development/strategic-claude-base (2 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 889 tokens. 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 commands, from other repositories
adr-backfill
Audit code, documentation, and history for potential architecture decisions that were never recorded, then return a deduplicated evidence report. Read-only.
adr-draft
Draft one new ADR from a current decision or a selected backfill handoff. Writes a single new record, as proposed.
adr-check
Check the current change, or a plan, against the decisions that govern it and report a verdict per decision. Read-only.
adr-queue
Show the review queue — every decision still proposed, with its SLA state — so open questions are visible before they are planned around. Read-only.
adr-context
Load the architecture decisions that govern the paths you are about to change, before planning against them. Read-only.
check
Check a produced plan against the decisions that govern it. Read-only.