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.
npx agentmods add commands/davidmatousek/agentic-oriented-development-kit/aod.scoregit clone --depth 1 https://github.com/davidmatousek/agentic-oriented-development-kitWhat 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.
| Model | Per session | Once 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 |
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.
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.
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
- Parse idea identifier from
$ARGUMENTS - Accept three formats:
NNN(bare number),#NNN(hash-prefixed), orIDEA-NNN(legacy) - If invalid or missing: Display usage
Usage: /aod.score NNN(or#NNNorIDEA-NNN)
Step 2: Execute Re-Scoring
Follow the workflow defined in the ~aod-score skill (.claude/skills/~aod-score/SKILL.md):
- Find GitHub Issue: For numeric input, call
aod_gh_find_issue NNN; for legacy IDEA-NNN, callaod_gh_find_issue "[IDEA-NNN]" - Read issue body to extract current ICE scores and status
- Display current ICE scores and status
- Present new ICE scoring via AskUserQuestion (Impact, Confidence, Effort — each H9/M6/L3 or custom 1-10)
- Compute new total, apply status transitions (threshold crossings, Validated preserved, Rejected re-opens)
- Update GitHub Issue body with new scores and status
- Add re-score comment to issue
- Regenerate BACKLOG.md via
.aod/scripts/bash/backlog-regenerate.sh - 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
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.
- 2d ago First seen · 51 lines · 11 tokens per session scan A 0cbc910fc7bb
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.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
speckit.auto
Automatically execute the four core phases of the Spec-Driven Development (SDD) pipeline: specify → plan → tasks → implement, in strict sequential order.
daily-priorities
Query DIGI Jira via the Atlassian MCP to build a prioritized daily work plan. The report has two parts: suggested priorities (the recommendation) and full context (everything you need to evaluate whether the suggestions are right and what else is on the docket).
OPSX: Bulk Archive
Archive multiple completed changes at once.
sync-linear
Sync current work with Linear ticket status.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).