Borrowing it
Nothing to install: this file belongs to wbern/agent-instructions. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/wbern/agent-instructions/main/.claude/commands/create-adr.mdgit clone --depth 1 https://github.com/wbern/agent-instructionsWrote 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/wbern/agent-instructions/create-adr)<a href="https://agentmods.dev/commands/wbern/agent-instructions/create-adr"><img src="https://agentmods.dev/badge/commands/wbern/agent-instructions/create-adr/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/commands/wbern/agent-instructions/create-adr"><img src="https://agentmods.dev/badge/commands/wbern/agent-instructions/create-adr.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.00009 | $0.01730 |
| Opus 5.5 | $0.00004 | $0.00692 |
| Sonnet 5.5 | $0.00002 | $0.00346 |
| Haiku 4.5 | $0.00001 | $0.00173 |
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 2mo 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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create ADR: Architecture Decision Record Creator
Create a new ADR to document an architectural decision. ADRs capture the "why" behind technical choices, helping future developers understand constraints and tradeoffs.
ADRs were introduced by Michael Nygard in 2011. The core structure (Context, Decision, Consequences) remains the standard.
General Guidelines
Output Style
- Never explicitly mention TDD in code, comments, commits, PRs, or issues
- Write natural, descriptive code without meta-commentary about the development process
- The code should speak for itself - TDD is the process, not the product
Beads is available for task tracking. Use mcp__beads__* tools to manage issues (the user interacts via bd commands).
Plan File Restriction
NEVER create, read, or update plan.md files. Claude Code's internal planning files are disabled for this project. Use other methods to track implementation progress (e.g., comments, todo lists, or external tools).
User arguments:
Create-adr: $ARGUMENTS
End of user arguments
(If no input provided, ask user for the architectural decision topic)
Process
Step 1: Detect Existing ADR Setup
Check for existing ADR directory and structure:
# Check common ADR directories (in order of preference)
for dir in doc/adr docs/adr decisions doc/architecture/decisions; do
if [ -d "$dir" ]; then
echo "Found: $dir"
ls "$dir"/*.md 2>/dev/null
break
fi
done
If ADRs exist: Read the first few ADRs (especially 0001 if present) to understand:
- The template/structure this project uses
- Any project-specific sections or frontmatter
- Naming conventions and style
Adapt the new ADR to match the existing pattern.
If no ADR directory exists: Run the initialization flow (Step 1b).
Step 1b: Initialize ADR Practice (First-Time Setup)
When no existing ADRs are found, help the user set up their ADR practice.
Ask the user (use AskUserQuestion):
Directory location:
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.
- 2mo ago First seen · 252 lines · 9 tokens per session scan A f532b9ea2002
create-adr is a command published in the GitHub repository wbern/agent-instructions (168 stars, last pushed 5mo ago), licensed MIT. It adds 9 tokens to every session and 1,730 once invoked, about $0.0000 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 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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.