aod.score

A command for updating an existing idea's ICE score: its expected impact, confidence, and effort. The idea is stored as a GitHub Issue, a GitHub page used to track work and discussion.

In plain words
What is it for?
Use it to find an idea by number, review its current score, enter new ratings, update the GitHub Issue, and regenerate BACKLOG.md.
Why use it?
It prevents old priorities from guiding decisions after circumstances or information change. It also keeps the issue and backlog aligned with the new score.

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/davidmatousek/agentic-oriented-development-kit/aod.score
Clone the repo
git clone --depth 1 https://github.com/davidmatousek/agentic-oriented-development-kit

Made for: Claude Code.

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 516 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00011 $0.00516
Opus 5 $0.00005 $0.00258
Sonnet 5 $0.00002 $0.00103
Haiku 4.5 $0.00001 $0.00052

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

Security

Grade A, and why

aod.score 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.

Origin

This is a copy

100% identical to aod.score — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/aod.score.md · 51 lines

What it actually says

User Input

$ARGUMENTS

Consider user input before proceeding (if not empty).

Overview

Updates an existing idea's ICE score when circumstances change, new information emerges, or priorities shift.

Source of truth: GitHub Issues. Reads and updates the idea's GitHub Issue body.

Flow: Parse identifier (NNN, #NNN, or IDEA-NNN) → Find GitHub Issue → Display current scores → New ICE scoring → Update status → Update GitHub Issue → Regenerate BACKLOG.md → Report comparison

Step 1: Validate Input

  1. Parse idea identifier from $ARGUMENTS
  2. Accept three formats: NNN (bare number), #NNN (hash-prefixed), or IDEA-NNN (legacy)
  3. If invalid or missing: Display usage Usage: /aod.score NNN (or #NNN or IDEA-NNN)

Step 2: Execute Re-Scoring

Follow the workflow defined in the ~aod-score skill (.claude/skills/~aod-score/SKILL.md):

  1. Find GitHub Issue: For numeric input, call aod_gh_find_issue NNN; for legacy IDEA-NNN, call aod_gh_find_issue "[IDEA-NNN]"
  2. Read issue body to extract current ICE scores and status
  3. Display current ICE scores and status
  4. Present new ICE scoring via AskUserQuestion (Impact, Confidence, Effort — each H9/M6/L3 or custom 1-10)
  5. Compute new total, apply status transitions (threshold crossings, Validated preserved, Rejected re-opens)
  6. Update GitHub Issue body with new scores and status
  7. Add re-score comment to issue
  8. Regenerate BACKLOG.md via .aod/scripts/bash/backlog-regenerate.sh
  9. Report old vs new comparison with tier change if applicable

Quality Checklist

  • Idea identifier validated (NNN, #NNN, or IDEA-NNN)
  • GitHub Issue found for the idea
  • Current scores displayed
  • New ICE score computed correctly
  • Status transitions applied correctly
  • GitHub Issue updated (body + comment)
  • BACKLOG.md regenerated
  • Comparison reported
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 · 51 lines · 11 tokens per session scan A 0cbc910fc7bb

Subscribe to this mod's changes

aod.score is a command published in the GitHub repository davidmatousek/agentic-oriented-development-kit (22 stars, last pushed 2mo ago), licensed MIT. It adds 11 tokens to every session and 516 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to aod.score, differing in 0 lines, and is treated as a copy.