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-foundationnpx skills add davidmatousek/agentic-oriented-development-kit --skill aod-foundationgit 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.00098 | $0.05530 |
| Opus 5 | $0.00049 | $0.02765 |
| Sonnet 5 | $0.00020 | $0.01106 |
| Haiku 4.5 | $0.00010 | $0.00553 |
Grade A, and why
aod-foundation 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.
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-foundation — 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 — 533 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aod.foundation Skill
Purpose
Guided post-init workshop with two parts:
- Part 1 (Vision): 5 storytelling-arc questions that populate
product-vision.md - Part 2 (Design): Archetype browser that generates
brands/{project-name}/files
Run after make init to replace placeholder markers with real content.
Step 0: Parse Flags
Parse --vision and --design flags from the user's arguments.
- If arguments contain
--vision:- Set
vision_only = true - Strip
--visionfrom arguments
- Set
- If arguments contain
--design:- Set
design_only = true - Strip
--designfrom arguments
- Set
- If neither flag is present:
- Set
run_both = true(full workshop)
- Set
- If both flags are present:
- Treat as
run_both = true(equivalent to no flags)
- Treat as
Step 1: State Detection
Detect the current project state to determine which parts to activate and whether this is a first-run or re-run.
1a: Derive Project Name
Use this ordered fallback to determine {project-name}:
- Repository directory name: Run
basename $(git rev-parse --show-toplevel)— use this if it yields a non-empty value - CLAUDE.md PROJECT_NAME: Read
CLAUDE.md, grep for a line matchingPROJECT_NAMEthat does NOT contain{{PROJECT_NAME}}(the un-replaced placeholder). Extract the value. - AskUserQuestion fallback: If neither source yields a usable name, ask: "What is your project name?" with a text input.
Sanitize the derived name to kebab-case: lowercase, replace spaces/underscores with hyphens, strip non-alphanumeric/non-hyphen characters.
Store as project_name for use throughout the workshop.
1b: Check Vision State
Read docs/product/01_Product_Vision/product-vision.md:
- If the file does not exist: Set
vision_state = "missing"— Part 1 will create from scratch - If the file contains
[To be refinedor[To be defined: Setvision_state = "placeholder"— Part 1 activates normally - If the file exists with no placeholder markers: Set
vision_state = "populated"— Part 1 enters re-run mode
What ships with it
1 file 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.
- 3d ago First seen · 533 lines · 98 tokens per session scan A 7afe38152eb1
aod-foundation is a skill published in the GitHub repository davidmatousek/agentic-oriented-development-kit (22 stars, last pushed 2mo ago), licensed MIT. It adds 98 tokens to every session and 5,530 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to aod-foundation, 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…