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 skills/davidmatousek/agentic-oriented-development-kit/aod-orchestratenpx skills add davidmatousek/agentic-oriented-development-kit --skill aod-orchestrategit 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.00110 | $0.10187 |
| Opus 5 | $0.00055 | $0.05094 |
| Sonnet 5 | $0.00022 | $0.02037 |
| Haiku 4.5 | $0.00011 | $0.01019 |
Grade A, and why
aod-orchestrate scanned grade A with 1 finding 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.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sf "${AOD_API_URL:-http://localhost:8000}/api/v1/projects/{project_id}" -H "X-AOD-Source: skill" This is a copy
100% identical to aod-orchestrate — 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 — 986 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aod.orchestrate Skill
Purpose
Orchestrate multiple features from /aod.blueprint output as priority-ordered parallel waves. The skill auto-detects the project, fetches actionable issues, groups them by ICE priority tier, and executes waves sequentially via the batch spawn API with governance checkpoints at tier boundaries.
Flow: Parse flags --> Auto-detect project --> Check idempotency --> Fetch issues --> Plan waves --> Confirm --> Execute waves --> Report completion
Step 0: Capture Start Time
Record the orchestration start time for duration calculation in the completion report.
Run the following command via Bash tool and store the result:
date +%s
Store this value as start_time for use in Step 8 (Completion Reporter).
Step 1: Parse Arguments
Parse user arguments from the skill invocation.
User Input
$ARGUMENTS
1.1: Parse --issues flag
Check if $ARGUMENTS contains --issues:
- If
$ARGUMENTScontains--issues N,N,N(comma-separated issue numbers):- Extract the comma-separated list of issue numbers
- Set
selected_issuesto the parsed list of integers - Strip
--issues N,N,Nfrom$ARGUMENTS(trim extra whitespace)
- If
$ARGUMENTSdoes NOT contain--issues:- Set
selected_issuesto empty (all issues)
- Set
1.2: Parse --dry-run flag
Check if $ARGUMENTS contains --dry-run:
- If present:
- Set
dry_run = true - Strip
--dry-runfrom$ARGUMENTS
- Set
- If not present:
- Set
dry_run = false
- Set
1.3: Parse --yes flag
Check if $ARGUMENTS contains --yes:
- If present:
- Set
auto_confirm = true - Strip
--yesfrom$ARGUMENTS
- Set
- If not present:
- Set
auto_confirm = false
- Set
Step 2: Project Auto-Detection
Resolve the active orchestrator project from local context. Detection follows a priority order with fallback.
2.1: Read config file
Run the following command via Bash tool:
cat .aod/config.json 2>/dev/null
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.
- 3d ago First seen · 986 lines · 110 tokens per session scan A 3d02470843d8
aod-orchestrate is a skill published in the GitHub repository davidmatousek/agentic-oriented-development-kit (22 stars, last pushed 2mo ago), licensed MIT. It adds 110 tokens to every session and 10,187 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to aod-orchestrate, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
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.
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.
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…