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/kb-createnpx skills add davidmatousek/agentic-oriented-development-kit --skill kb-creategit 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.00073 | $0.03775 |
| Opus 5 | $0.00036 | $0.01887 |
| Sonnet 5 | $0.00015 | $0.00755 |
| Haiku 4.5 | $0.00007 | $0.00378 |
Grade A, and why
kb-create 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl http://localhost:3000/health This is a copy
100% identical to kb-create — 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 — 632 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KB Create Skill
Purpose
Guided pattern and bug creation with interactive prompts, automatic quality validation, and improvement suggestions. Ensures high-quality KB entries that meet institutional knowledge standards.
Decision Tree: Pattern vs Bug
Should I create a PATTERN or BUG entry?
START: Do you have a reusable solution or specific error fix?
↓
Is this a specific error with an exact error message?
→ YES: Is the solution configuration/environment-specific?
→ YES: Create BUG entry
→ NO: Could be either - is it reusable across projects?
→ YES: Create PATTERN
→ NO: Create BUG
→ NO: Is this a general solution to a common problem?
→ YES: Create PATTERN
→ NO: Is it a design decision or architectural guidance?
→ YES: Create PATTERN
→ NO: Maybe not KB-worthy - consider documentation instead
Pattern: Reusable solutions, design patterns, best practices, architectural guidance Bug: Specific errors with exact error messages, environment issues, configuration fixes
Pattern Creation Workflow
Step 1: Collect Basic Information
Creating new KB Pattern
Required fields (asterisk = required):
* Title (10-100 characters):
→ Example: "PostgreSQL Connection Pool Optimization"
* Category (select one):
1. ARCH (Architecture & Design)
2. DB (Database)
3. API (API Design)
4. AUTH (Authentication)
5. SECURITY (Security)
6. TEST (Testing)
7. PERF (Performance)
8. FRONTEND (Frontend)
9. INFRA (Infrastructure)
10. DEPLOY (Deployment)
11. CACHE (Caching)
12. MCP (MCP Servers)
13. CLIENT (Client Integration)
14. FLOW (Workflows)
→ Your choice (1-14):
* Keywords (min 5, comma-separated):
→ Example: postgresql, connection-pool, optimization, performance, scaling
→ Your keywords:
Step 2: Define Problems Solved
* Problems this pattern solves (min 2, max 10):
Problem 1:
→ Example: Connection pool exhaustion under high load
Problem 2:
→ Example: Slow query performance due to connection limits
Problem 3 (or Enter to continue):
→ Example: Connection timeout errors during peak traffic
... (continue until Enter on empty line)
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 · 632 lines · 73 tokens per session scan A 634b8084e3de
kb-create is a skill published in the GitHub repository davidmatousek/agentic-oriented-development-kit (22 stars, last pushed 2mo ago), licensed MIT. It adds 73 tokens to every session and 3,775 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to kb-create, 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.