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-specnpx skills add davidmatousek/agentic-oriented-development-kit --skill aod-specgit 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.00071 | $0.01617 |
| Opus 5 | $0.00036 | $0.00809 |
| Sonnet 5 | $0.00014 | $0.00323 |
| Haiku 4.5 | $0.00007 | $0.00162 |
Grade A, and why
~aod-spec 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Validator Skill
Purpose
Automatically validates specification files (spec.md) for completeness, quality, and readiness for architecture and implementation phases. Implements FR-004 from the feature specification.
How It Works
Step 1: Locate Specification
- Search for
specs/*/spec.mdfiles in the repository - If specific feature directory provided, validate that spec.md
- Report if spec.md not found
Step 2: Validate Mandatory Sections
Check for required sections per specification template:
-
User Scenarios & Testing (mandatory)
- User stories with acceptance scenarios
- Independent test criteria
- Edge cases identified
-
Requirements (mandatory)
- Functional requirements
- Key entities
-
Success Criteria (mandatory)
- Measurable outcomes
-
Scope (mandatory)
- In scope
- Out of scope
-
Assumptions (optional but recommended)
-
Dependencies (optional but recommended)
-
References (optional)
Step 3: Check for Clarification Markers
- Grep for
[NEEDS CLARIFICATION]markers - Report all instances with line numbers
- Specification not ready if any markers remain
Step 4: Validate Testable Criteria
- Check that each user story has clear acceptance scenarios
- Verify success criteria are measurable (contain numbers/percentages)
- Ensure requirements have validation criteria
Step 5: Check Scope Boundaries
- Verify "In Scope" section exists and is populated
- Verify "Out of Scope" section exists (clear boundaries)
- Check that scope is clearly bounded (not open-ended)
Step 6: Generate Validation Report
Report format:
Specification Validation Report
File: specs/{feature-id}/spec.md
Mandatory Sections:
- [✓/✗] User Scenarios & Testing
- [✓/✗] Requirements (Functional Requirements)
- [✓/✗] Success Criteria
- [✓/✗] Scope (In/Out)
Quality Checks:
- [✓/✗] No [NEEDS CLARIFICATION] markers
- [✓/✗] All requirements testable
- [✓/✗] Scope clearly bounded
- [✓/✗] Success criteria measurable
Status: READY / NOT READY
Issues Found:
1. [Issue description with line number]
2. [Issue description with line number]
Recommendations:
- [Specific action to resolve each issue]
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.
- 2d ago First seen · 214 lines · 71 tokens per session scan A 9e195194072b
~aod-spec is a skill published in the GitHub repository davidmatousek/agentic-oriented-development-kit (22 stars, last pushed 2mo ago), licensed MIT. It adds 71 tokens to every session and 1,617 once invoked, about $0.0004 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.
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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…