~aod-run

A workflow coordinator for taking a software idea through six stages: discovery, definition, planning, building, delivery, and documentation. It saves progress to disk and pauses for required approvals between stages.

In plain words
What is it for?
Use it to start work from an idea, continue an issue from its current stage, resume from a saved checkpoint, or view progress.
Why use it?
It keeps a long development process organized and resumable, even if a session stops. It also makes approval points visible before work moves forward.

Skill for Claude CodeCodex

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 skills/davidmatousek/agentic-oriented-development-kit/aod-run
Any agent
npx skills add davidmatousek/agentic-oriented-development-kit --skill aod-run
Clone the repo
git clone --depth 1 https://github.com/davidmatousek/agentic-oriented-development-kit

Made for: Claude Code, Codex.

Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 10,107 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.00072 $0.10107
Opus 5 $0.00036 $0.05053
Sonnet 5 $0.00014 $0.02021
Haiku 4.5 $0.00007 $0.01011

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

Security

Grade A, and why

~aod-run 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.

.claude/skills/~aod-run/SKILL.md · 694 lines

How it starts

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

Full Lifecycle Orchestrator Skill

Purpose

Single-command lifecycle orchestrator that chains all 6 AOD stages autonomously, pausing at governance gates for Triad sign-offs and persisting state to disk for session resilience. After Deliver completes, Document runs automatically as Stage 6.

Entry Points:

  • Raw idea: "description" → start at Discover
  • Issue number: #NNN or NNN → resume from issue's current stage
  • Resume: --resume → continue from last state checkpoint
  • Status: --status / --status #NNN → read-only display

State File: .aod/run-state.json (atomic write-then-rename via run-state.sh)

Section Purpose Location
Step 1: Route by Mode Entry point routing This file
Step 2: Core State Machine Loop Central orchestration logic This file
Plan Substage Tracking Spec → project_plan → tasks This file
Stage Skill Mapping Stage-to-skill invocation table This file
Post-Stage Context Extraction Artifact discovery after each stage This file
Stage Map Display Visual progress indicators This file
Transition Messages Stage transition headers This file
GitHub Integration Label updates after stage completion This file
Error Logging Error/event capture in state file This file
Governance Gate Detection Reading approval/rejection from frontmatter references/governance.md
Governance Tier Light/Standard/Full gate rules references/governance.md
Rejection / Retry / Circuit Breaker / Blocked Governance result handling references/governance.md
New Idea / Issue / Resume / Status Entry Mode-specific handlers references/entry-modes.md
Dry-Run Entry --dry-run preview handler (read-only) references/dry-run.md
Corrupted State / Lifecycle Complete Error and completion handlers references/error-recovery.md

Read the full file on GitHub · 694 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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 · 694 lines · 72 tokens per session scan A bd890355e021

Subscribe to this mod's changes

~aod-run is a skill published in the GitHub repository davidmatousek/agentic-oriented-development-kit (22 stars, last pushed 2mo ago), licensed MIT. It adds 72 tokens to every session and 10,107 once invoked, about $0.0004 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-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens