decision-log

decision-log is a command for coding agents from Dokkabei97/forged-claude-code. It costs 25 tokens per session (1,266 once invoked), scanned A, original, MIT.

A command that records important technical, product, business or process decisions as decision records. Each record captures the context, alternatives, chosen option, reasoning and consequences.

In plain words
What is it for?
Use it to create, list and review records such as architecture choices, library selections, feature priorities, hiring decisions and workflow changes.
Why use it?
It preserves why a decision was made, so future contributors do not have to reconstruct the discussion or repeat the same evaluation.

Command

Part of the forged-claude-code plugin — 29 skills, 14 commands, 9 agents, 2 hooks shipped together

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.

agentmods
npx agentmods add commands/dokkabei97/forged-claude-code/decision-log
Clone the repo
git clone --depth 1 https://github.com/Dokkabei97/forged-claude-code

Or install forged-claude-code, the plugin that ships this one along with the rest of its 29 skills, 14 commands, 9 agents, 2 hooks.

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/dokkabei97/forged-claude-code/decision-log.svg)](https://agentmods.dev/commands/dokkabei97/forged-claude-code/decision-log)
Your own site
<a href="https://agentmods.dev/commands/dokkabei97/forged-claude-code/decision-log"><img src="https://agentmods.dev/badge/commands/dokkabei97/forged-claude-code/decision-log.svg" alt="Measured on agentmods" height="20"></a>
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,266 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00025 $0.01266
Opus 5 $0.00013 $0.00633
Sonnet 5 $0.00005 $0.00253
Haiku 4.5 $0.00003 $0.00127

Measured 4d ago against content hash 3cb62af00fb1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

commands/decision-log.md · 179 lines

How it starts

The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/decision-log - Decision Record Generator

Triggers

  • When a significant decision is made (technical, product, business)
  • When someone asks "why did we decide to..."
  • When documenting the rationale behind a choice for future reference

Usage

/decision-log [decision title]
/decision-log "Use Supabase instead of Firebase"
/decision-log --list                    # Show all recorded decisions
/decision-log --review [ID]            # Review a past decision

Behavioral Flow

Phase 1: Determine Decision Context

Identify what type of decision is being recorded:

Category Examples
Technical Stack choice, architecture pattern, library selection
Product Feature priority, UX approach, pricing model
Business Hiring, partnership, market focus
Process Workflow change, tool adoption, meeting cadence

Phase 2: Gather Decision Details

Prompt for or extract from conversation:

  1. Title: One-line summary of the decision
  2. Context: What problem or situation prompted this decision?
  3. Options Considered: What alternatives were evaluated?
  4. Decision: What was chosen?
  5. Rationale: Why was this option selected?
  6. Consequences: What are the expected outcomes and trade-offs?

Phase 3: Generate Decision Record

# DR-[NNNN]: [Decision Title]

| Field | Value |
|-------|-------|
| **Date** | YYYY-MM-DD |
| **Status** | Proposed / Accepted / Deprecated / Superseded |
| **Category** | Technical / Product / Business / Process |
| **Deciders** | [Names/Roles] |
| **Supersedes** | DR-[NNNN] (if applicable) |

## Context
[2-3 sentences describing the situation, problem, or opportunity that
prompted this decision. Include constraints and requirements.]

## Options Considered

### Option A: [Name]
- **Pros**: [advantages]
- **Cons**: [disadvantages]
- **Cost/Effort**: [estimate]

### Option B: [Name]
- **Pros**: [advantages]
- **Cons**: [disadvantages]
- **Cost/Effort**: [estimate]

### Option C: [Name] (if applicable)
- **Pros**: [advantages]
- **Cons**: [disadvantages]
- **Cost/Effort**: [estimate]

## Decision
**We chose Option [X]: [Name].**

## Rationale
[Why this option was selected over others. Be specific about the
deciding factors and how they mapped to our current constraints.]

## Consequences

### Positive
- [Expected benefit 1]
- [Expected benefit 2]

### Negative / Trade-offs
- [Accepted trade-off 1]
- [Accepted trade-off 2]

### Risks
- [Risk 1] — Mitigation: [plan]

## Review Date
[When should this decision be revisited? e.g., "After reaching 10K users"
or "Q3 2026" or "When [condition] changes"]

Read the full file on GitHub · 179 lines

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. 4d ago First seen · 179 lines · 25 tokens per session scan A 3cb62af00fb1

Subscribe to this mod's changes

decision-log is a command published in the GitHub repository Dokkabei97/forged-claude-code (2 stars, last pushed 6mo ago), licensed MIT. It adds 25 tokens to every session and 1,266 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.