agentmods.dev

~aod-build

A checkpoint-report generator for multi-stage software implementation work.

In plain words
What is it for?
Use it when a project phase, user story, or major feature is complete, or before stopping work for review or feedback.
Why use it?
It makes pauses and milestones easier to understand by recording completed work, remaining tasks, progress, quality results, and how to continue.

Skill for Claude CodeCodex

22 2mo ago A scan 56 tokens original MIT
View the source file davidmatousek/agentic-oriented-development-kit
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-build
Any agent
npx skills add davidmatousek/agentic-oriented-development-kit --skill aod-build
Clone the repo
git clone --depth 1 https://github.com/davidmatousek/agentic-oriented-development-kit

Made for: Claude Code, Codex.

Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,510 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.00056 $0.02510
Opus 5 $0.00028 $0.01255
Sonnet 5 $0.00011 $0.00502
Haiku 4.5 $0.00006 $0.00251

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

Security

Grade A, and why

~aod-build 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 3d ago.

The scan reads SKILL.md. This mod also ships 3 executable files (scripts/analyze_tasks.py, scripts/generate_checkpoint.py, scripts/update_index.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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-build/SKILL.md · 338 lines

How it starts

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

Implementation Checkpoint Skill

Purpose

Automatically generate standardized checkpoint reports that document implementation progress at strategic milestones. Each report includes completed tasks, remaining work, technical achievements, knowledge base entries, quality metrics, and resume instructions.

When to Use

Create a checkpoint at:

  1. Complete phase finish - All tasks in a phase marked complete
  2. User story completion - Entire user story implemented and tested
  3. Critical milestone - Core functionality ready (e.g., MVP core)
  4. Before pausing - Stopping for review, testing, or user feedback
  5. After architect review - Major approval/sign-off received

How to Use

Quick Usage

# Navigate to skill directory
cd .claude/skills/~aod-build

# Generate checkpoint (interactive prompts will follow)
python scripts/generate_checkpoint.py \
  --tasks-file ../../specs/{feature-id}/tasks.md \
  --output-dir ../../specs/{feature-id} \
  --description "{Phase-Description}"

Step-by-Step Process

  1. Analyze completion status

    # Script automatically:
# - Reads tasks.md
# - Counts [X] completed vs [ ] pending
# - Calculates progress percentage
# - Identifies completed phases
# - Determines task range

  2. Provide context when prompted

    Key achievements (3-5 bullet points):
> - Achievement 1
> - Achievement 2
> - Achievement 3

Knowledge base entries captured (count or 'none'):
> 2

[For each KB entry, provide: Title, Problem, Solution]

  3. Review generated report

    # Output: CHECKPOINT-{NN}_{Description}_{TaskRange}.md
# Location: specs/{feature-id}/

  4. Verify index updated

    # Check: CHECKPOINTS_README.md includes new checkpoint

Checkpoint Naming Convention

Format: CHECKPOINT-{NN}_{Phase-Description}_{TaskRange}.md

Components:

  • {NN}: Sequential checkpoint number (01, 02, 03...) - auto-detected
  • {Phase-Description}: Milestone name (e.g., "Phase1-2-Complete", "US1-Complete")
  • {TaskRange}: Task IDs covered (e.g., "T001-T030")

Read the full file on GitHub · 338 lines

Files

What ships with it

9 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. 3d ago First seen · 338 lines · 56 tokens per session scan A 610e720fee5e

Subscribe to this mod's changes

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

PlanningProject management
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