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/create_adrgit 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/create_adr)<a href="https://agentmods.dev/commands/fomo-driven-development/strategic-claude-base/create_adr"><img src="https://agentmods.dev/badge/commands/fomo-driven-development/strategic-claude-base/create_adr.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.00011 | $0.01676 |
| Opus 5 | $0.00005 | $0.00838 |
| Sonnet 5 | $0.00002 | $0.00335 |
| Haiku 4.5 | $0.00001 | $0.00168 |
Grade A, and why
create_adr 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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are tasked with creating focused, well-structured Architecture Decision Record (ADR) documentation for architectural decisions. You should be efficient, focused, and avoid extensive research - document the decision context you know.
Decision Context/Subject provided: $1
Initial Response
When this command is invoked:
-
Check if decision context/subject was provided:
- If context/subject was provided as parameter, proceed with analysis
- If no context provided, respond with:
I'll help you create an Architecture Decision Record (ADR) for an architectural decision. Please provide: 1. A description of the architectural decision context, or 2. A plan/research file path to extract decisions from Examples: - `/create_adr database technology selection for user service` - `/create_adr @.strategic-claude-basic/plan/PLAN_0001_07-09-2025_sat_user-auth.md` I'll document the architectural decision without extensive research.Then wait for the user's input.
Process Steps
Step 1: Input Analysis
-
Determine input type:
If it's a file path (starts with @. or contains .md):
- Read the specified file completely
- Look for sections about architectural decisions, technology choices, or design approaches
- Prepare to create multiple ADRs if needed
If it's a decision context:
- Use the provided context as the decision subject
- Look at conversation context for additional details about alternatives, rationale
- Prepare to create a single ADR
-
Present scope:
For file input:
Reading file: [filename] Found [N] architectural decisions to document: - [Brief decision 1] - [Brief decision 2] - [Brief decision 3] I'll create individual ADR documents for each decision found. Proceeding with ADR creation...For context input:
Creating ADR documentation for: [decision context] I'll document this architectural decision based on the current context and known details. Proceeding with ADR creation...
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 · 247 lines · 11 tokens per session scan A bb47fafa43b7
create_adr is a command published in the GitHub repository Fomo-Driven-Development/strategic-claude-base (2 stars, last pushed 9mo ago), licensed MIT. It adds 11 tokens to every session and 1,676 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.