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-blueprintnpx skills add davidmatousek/agentic-oriented-development-kit --skill aod-blueprintgit clone --depth 1 https://github.com/davidmatousek/agentic-oriented-development-kitWrote 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-blueprint)<a href="https://agentmods.dev/skills/davidmatousek/agentic-oriented-development-kit/aod-blueprint"><img src="https://agentmods.dev/badge/skills/davidmatousek/agentic-oriented-development-kit/aod-blueprint.svg" alt="Measured on agentmods" 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 | $0.00098 | $0.04048 |
| Opus 5 | $0.00049 | $0.02024 |
| Sonnet 5 | $0.00020 | $0.00810 |
| Haiku 4.5 | $0.00010 | $0.00405 |
Grade A, and why
~aod-blueprint 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 4d 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}/health -H "X-AOD-Source: skill" How it starts
The opening of the file, as written. The whole thing — 419 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aod.blueprint Skill
Purpose
Unified project setup and story generation in a single command. The skill auto-detects whether the current project is new or existing, then runs the appropriate workflow:
- First-Run -- Creates GitHub repo, registers project with orchestrator API, activates it, runs interactive intake, generates stories, creates issues
- Subsequent-Run -- Skips setup, runs interactive intake, generates new stories with deduplication against existing issues
- Demo Mode (
--demo) -- Loads pre-built Hello World stories fromHELLO_WORLD_STORIES.md, skips interactive intake entirely
All modes end with issue creation, lifecycle sync, consumer guide generation, and a completion report.
Step 0: Prerequisites Check
Validate that required tools and services are available before proceeding.
0.1: Check gh CLI
Run gh --version via Bash tool.
- If the command succeeds, continue to Step 0.2.
- If the command fails, display the following error and STOP:
ERROR: GitHub CLI (gh) is not installed or not in PATH.
Install it from https://cli.github.com/ and run `gh auth login` to authenticate.
0.2: Check API Health
Run the following command via Bash tool:
curl -sf ${AOD_API_URL:-http://localhost:8000}/health -H "X-AOD-Source: skill"
- If the command succeeds (exit code 0), display "Prerequisites OK" and continue to Step 1.
- If the command fails, display the following error and STOP:
ERROR: AOD Orchestrator API is not reachable at ${AOD_API_URL:-http://localhost:8000}.
Start the API with `make run` and try again.
Step 1: Auto-Detection
Determine the project name, check for an existing project in the orchestrator, and set the execution mode.
1.1: Derive Project Name
Run git remote get-url origin via Bash tool.
- If the command succeeds, extract the repo name from the URL: take the last path segment and strip any
.gitsuffix. For example,https://github.com/org/my-project.gityieldsmy-project. Store as{project_name}. - If the command fails (no remote configured), run
basename $(pwd)via Bash tool and store the result as{project_name}.
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.
- 4d ago First seen · 419 lines · 98 tokens per session scan A fe7f400cf478
~aod-blueprint 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 4,048 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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…