Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/davidmatousek/agentic-oriented-development-kitnpx agentmods add skills/davidmatousek/agentic-oriented-development-kit/aod-deliverWrote 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.
[](https://agentmods.dev/skills/davidmatousek/agentic-oriented-development-kit/aod-deliver)<a href="https://agentmods.dev/skills/davidmatousek/agentic-oriented-development-kit/aod-deliver"><img src="https://agentmods.dev/badge/skills/davidmatousek/agentic-oriented-development-kit/aod-deliver/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/davidmatousek/agentic-oriented-development-kit/aod-deliver"><img src="https://agentmods.dev/badge/skills/davidmatousek/agentic-oriented-development-kit/aod-deliver.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00081 | $0.15396 |
| Opus 5.5 | $0.00032 | $0.06158 |
| Sonnet 5.5 | $0.00016 | $0.03079 |
| Haiku 4.5 | $0.00008 | $0.01540 |
Grade A, and why
~aod-deliver 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 1mo 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-deliver — 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.
How it starts
The opening of the file, as written. The whole thing — 1,184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AOD Deliver Skill
Purpose
Close a completed feature with a structured retrospective that captures delivery metrics, surprises, and lessons learned. New ideas from the retrospective feed back into the Discover stage, completing the AOD Lifecycle loop.
Entry point: /aod.deliver
Prerequisites
- A feature branch exists with completed work (typically after
/aod.build [--no-security] [--no-simplify] [--no-docs]) .aod/spec.mdexists with the feature specification.aod/tasks.mdexists with task definitions.aod/scripts/bash/github-lifecycle.shis available for GitHub operations
Reference-Loading Contract
Several sections of this skill are stored in on-demand reference files under .claude/skills/~aod-deliver/references/. This mirrors the ~aod-run pattern.
Trigger idiom (used at every reference load site below):
MANDATORY: You MUST use the Read tool to load
references/X.mdbefore proceeding with [task]. Do NOT rely on memory of prior [X] content. If the file cannot be read, display an error and STOP.
Fail-closed rule: If a reference file cannot be read at a gate, display an error message and STOP execution. Do not attempt to continue from memory.
Re-read rule: If more than 50 lines of interstitial output have been generated since a reference was last read, re-read it before using its content.
Reference Decision Table
| Reference File | Holds | Load When |
|---|---|---|
references/deliver-flags.md |
Step 0 + Step 0g (flag parse + audit log) | Every run — at Step 0 |
references/delivery-lock.md |
Step 0.5 (acquire lock) + Step 14 (release lock) | Every run — at Step 0.5 and Step 14 |
references/close-and-document.md |
Step 12 (close issue) + Step 13 (prompt /aod.document) | Every run — at Step 12 |
references/render-tables.md |
Step 11c.1 Feature-139 render tables | Only when e2e_validation.status is set (E2E was entered) |
references/edge-cases.md |
Edge Cases, Common Rationalizations, Red Flags | Only when handling an edge case or checking a rationalization/red-flag |
What ships with it
5 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.
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.
- 1mo ago First seen · 1,184 lines · 81 tokens per session scan A f084346e6884
~aod-deliver is a skill published in the GitHub repository davidmatousek/agentic-oriented-development-kit (24 stars, last pushed 3mo ago), licensed MIT. It adds 81 tokens to every session and 15,396 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to ~aod-deliver, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…