decision-log

decision-log is a command for Claude Code from AhmedHabiba/architor. It costs 0 tokens per session (93 once invoked), scanned A, original, MIT.

A command that reads and displays the recorded decisions for a software architecture project. The log is stored in a Markdown file, a plain-text document format.

In plain words
What is it for?
Use it to view all decisions or filter them by a phase or topic such as security or the database.
Why use it?
It provides one place to review why architecture choices were made instead of searching through earlier work.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Good fit Use it to view all decisions or filter them by a phase or topic such as security or the database.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/ahmedhabiba/architor/decision-log
Install

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.

Clone the repo
git clone --depth 1 https://github.com/AhmedHabiba/architor

Made for: Claude Code.

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.

agentmods badge for decision-log

README.md
[![agentmods](https://agentmods.dev/badge/commands/ahmedhabiba/architor/decision-log/github.svg)](https://agentmods.dev/commands/ahmedhabiba/architor/decision-log)
Your own site
<a href="https://agentmods.dev/commands/ahmedhabiba/architor/decision-log"><img src="https://agentmods.dev/badge/commands/ahmedhabiba/architor/decision-log/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.

agentmods 80×15 button for decision-log

Your own site · 80×15
<a href="https://agentmods.dev/commands/ahmedhabiba/architor/decision-log"><img src="https://agentmods.dev/badge/commands/ahmedhabiba/architor/decision-log.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 93 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00093
Opus 5 $0.00000 $0.00046
Sonnet 5 $0.00000 $0.00019
Haiku 4.5 $0.00000 $0.00009

Measured 9d ago against content hash 894470185a5e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

decision-log 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 9d 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.

.claude/commands/decision-log.md · 10 lines

What it actually says

Read .arch/decisions.md and display the full decision log.

If the file doesn't exist or is empty, say: "No decisions recorded yet. Decisions are logged as you progress through the phases."

If the file exists, display it formatted clearly, organized by phase.

If $ARGUMENTS contains a filter (e.g., "phase 2", "security", "database"), filter the decisions to show only matching entries.

$ARGUMENTS

Changes

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.

  1. 9d ago First seen · 10 lines · 0 tokens per session scan A 894470185a5e

Subscribe to this mod's changes

decision-log is a command published in the GitHub repository AhmedHabiba/architor (6 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 93 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.