Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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_decision)<a href="https://agentmods.dev/commands/fomo-driven-development/strategic-claude-base/adr_decision"><img src="https://agentmods.dev/badge/commands/fomo-driven-development/strategic-claude-base/adr_decision.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.1 | $0.00016 | $0.01954 |
| Opus 5 | $0.00008 | $0.00977 |
| Sonnet 5 | $0.00003 | $0.00391 |
| Haiku 4.5 | $0.00002 | $0.00195 |
Grade A, and why
adr_decision 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 5d 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 — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are tasked with managing Architecture Decision Record (ADR) status transitions. You will update ADR documents through their lifecycle states: proposed → accepted/rejected, accepted → deprecated/superseded.
ADR file path and status flag provided: $1
Initial Response
When this command is invoked:
-
Check if ADR file path and flag were provided:
- If both ADR file path and status flag were provided, proceed with validation
- If missing parameters, respond with:
I'll help you update an ADR's status through its lifecycle. Usage: `/adr_decision <adr_file_path> <--flag>` Available flags: - `--accept`: Change proposed ADR to accepted - `--reject`: Change proposed ADR to rejected - `--deprecate`: Change accepted ADR to deprecated - `--supersede`: Change accepted/deprecated ADR to superseded Examples: - `/adr_decision @.strategic-claude-basic/decisions/ADR_0001_17-09-2025_wed_backwards-compatibility-policy.md --accept` - `/adr_decision ADR_0001_17-09-2025_wed_backwards-compatibility-policy.md --supersede` Provide the ADR file path and the status transition flag.Then wait for the user's input.
Process Steps
Step 1: Input Validation and File Analysis
-
Parse command arguments:
- Extract ADR file path from first argument
- Extract status flag from second argument (--accept, --reject, --deprecate, --supersede)
- Validate flag is one of the four allowed options
-
Locate and read ADR file:
# If path doesn't start with ., add the decisions directory prefix if [[ "$adr_path" != ./* ]]; then adr_path=".strategic-claude-basic/decisions/$adr_path" fi -
Validate ADR file exists and read content:
- Check if file exists and is readable
- Read complete ADR document
- Extract current status from frontmatter
- Extract decision number for tracking
-
Present current state:
ADR Analysis: File: [filename] Decision: ADR-NNNN - [title] Current Status: [current_status] Requested Transition: [current_status] → [new_status] [Validation result: Valid/Invalid transition] Proceeding with status update...
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.
- 5d ago First seen · 291 lines · 16 tokens per session scan A f3abbf072499
adr_decision is a command published in the GitHub repository Fomo-Driven-Development/strategic-claude-base (2 stars, last pushed 9mo ago), licensed MIT. It adds 16 tokens to every session and 1,954 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
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.