log-decision

log-decision is a command for Claude Code from 16wells/claude-project-setup. It costs 8 tokens per session (199 once invoked), scanned A, original, MIT.

A command for adding a decision to a project's decisions log. It records whether the decision is closed, open, or still awaiting input, along with a date and short notes.

In plain words
What is it for?
Use it to record a completed decision, an unresolved question, or an item still needed from a client.
Why use it?
It keeps decisions, recent changes, and activity records aligned instead of leaving important choices only in conversation history.

Command for Claude Code

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/16wells/claude-project-setup/log-decision
Clone the repo
git clone --depth 1 https://github.com/16wells/claude-project-setup

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 log-decision

README.md
[![agentmods](https://agentmods.dev/badge/commands/16wells/claude-project-setup/log-decision.svg)](https://agentmods.dev/commands/16wells/claude-project-setup/log-decision)
Your own site
<a href="https://agentmods.dev/commands/16wells/claude-project-setup/log-decision"><img src="https://agentmods.dev/badge/commands/16wells/claude-project-setup/log-decision.svg" alt="Measured on agentmods" height="20"></a>
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 199 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.00008 $0.00199
Opus 5 $0.00004 $0.00100
Sonnet 5 $0.00002 $0.00040
Haiku 4.5 $0.00001 $0.00020

Measured 4d ago against content hash 6c73e5ac4c65, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

log-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 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.

templates/client-project/.claude/commands/log-decision.md · 19 lines

What it actually says

Add a new row to 01-context/decisions-log.md. The argument tells you which section:

  • closed → append to the Closed Decisions table with today's date, the decision, and a one-line rationale
  • open → append to the Open Decisions table with today's date, the decision, and notes on why it's open
  • outstanding → append to the Outstanding From Client table with the item, ⏳ Pending status, and notes

If the argument doesn't specify which section, ask the user before writing.

After adding the row, update the Change Log at the bottom of the file with today's date and a one-line description of what changed.

Also append a brief note to 01-context/activity-log.md referencing the decision so the activity log stays in sync.

Arguments: $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. 4d ago First seen · 19 lines · 0 tokens per session scan A 6c73e5ac4c65

Subscribe to this mod's changes

log-decision is a command published in the GitHub repository 16wells/claude-project-setup (2 stars, last pushed 6d ago), licensed MIT. It adds 8 tokens to every session and 199 once invoked, about $0.0000 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.