decision-new

decision-new is a command for Claude Code from IvanLutsenko/awac-ai-agent-plugins. It costs 10 tokens per session (392 once invoked), scanned A, original, MIT.

A command for recording an architecture decision: a note explaining an important technical choice, its context, and its consequences.

In plain words
What is it for?
Use it to create a decision record, optionally link related work, and add it to the project's tracking information.
Why use it?
It preserves why a project made a technical choice, so the reasoning is available later and can be related to tasks or bugs.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Part of the obsidian-tracker plugin — 19 skills, 19 commands shipped together

Good fit Use it to create a decision record, optionally link related work, and add it to the project's tracking information.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/ivanlutsenko/awac-ai-agent-plugins/decision-new
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/IvanLutsenko/awac-ai-agent-plugins

Made for: Claude Code.

Or install obsidian-tracker, the plugin that ships this one along with the rest of its 19 skills, 19 commands.

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-new

README.md
[![agentmods](https://agentmods.dev/badge/commands/ivanlutsenko/awac-ai-agent-plugins/decision-new.svg)](https://agentmods.dev/commands/ivanlutsenko/awac-ai-agent-plugins/decision-new)
Your own site
<a href="https://agentmods.dev/commands/ivanlutsenko/awac-ai-agent-plugins/decision-new"><img src="https://agentmods.dev/badge/commands/ivanlutsenko/awac-ai-agent-plugins/decision-new.svg" alt="Measured on agentmods" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 392 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.00010 $0.00392
Opus 5 $0.00005 $0.00196
Sonnet 5 $0.00002 $0.00078
Haiku 4.5 $0.00001 $0.00039

Measured 2d ago against content hash 697a198c3980, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

decision-new 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 2d 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.

plugins/obsidian-tracker/commands/decision-new.md · 43 lines

What it actually says

/decision-new — Create Decision

Steps

  1. Determine project:

    • If .claude/obsidian-tracking.json exists, use the project from it.
    • Otherwise, call findProjectByLocalPath with cwd.
    • If still no project, ask the user.
  2. Collect decision info:

    • If the user provided a description in the command argument, extract title/context/decision/consequences from it.
    • Otherwise ask via AskUserQuestion:
      • Title — short name for the decision
      • Context — what problem or situation led to this decision?
      • Decision — what was decided?
      • Consequences — what are the trade-offs?
  3. Check for related entities:

    • If tracking is active, check if current work relates to tasks or bugs.
    • Offer to link them (optional).
  4. Create the decision:

    • Call addDecision with all collected info.
  5. Update tracking:

    • If .claude/obsidian-tracking.json exists, add "📋 Decision DEC-{id}: {title}" to actions.
  6. Confirm with the decision ID and a brief summary.

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. 2d ago First seen · 43 lines · 10 tokens per session scan A 697a198c3980

Subscribe to this mod's changes

decision-new is a command published in the GitHub repository IvanLutsenko/awac-ai-agent-plugins (2 stars, last pushed 4d ago), licensed MIT. It adds 10 tokens to every session and 392 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-09-05.