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-lensnpx skills add davidmatousek/agentic-oriented-development-kit --skill aod-lensgit 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-lens)<a href="https://agentmods.dev/skills/davidmatousek/agentic-oriented-development-kit/aod-lens"><img src="https://agentmods.dev/badge/skills/davidmatousek/agentic-oriented-development-kit/aod-lens.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.00093 | $0.00857 |
| Opus 5 | $0.00046 | $0.00428 |
| Sonnet 5 | $0.00019 | $0.00171 |
| Haiku 4.5 | $0.00009 | $0.00086 |
Grade A, and why
aod-lens 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 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.
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-lens — 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Thinking Lens Skill
Router that selects and applies thinking methodologies from docs/core_principles/.
Keyword → Lens Routing
| Keywords | Lens | File |
|---|---|---|
| "failed", "broke", "why did", "root cause" | 5 Whys | 01-FIVE_WHYS_METHODOLOGY.md |
| "assumptions", "fundamentally", "from scratch" | First Principles | 02-FIRST_PRINCIPLES.md |
| "risks", "could go wrong", "before we start" | Pre-Mortem | 03-PRE_MORTEM.md |
| "guarantee failure", "avoid", "anti-patterns" | Inversion | 04-INVERSION.md |
| "prioritize", "most value", "80/20" | Pareto Analysis | 05-PARETO_ANALYSIS.md |
| "architecture", "interact", "components" | Systems Thinking | 06-SYSTEMS_THINKING.md |
| "consequences", "downstream", "side effects" | Second-Order Effects | 07-SECOND_ORDER_EFFECTS.md |
| "blocked", "bottleneck", "dependencies" | Constraint Analysis | 08-CONSTRAINT_ANALYSIS.md |
| "challenge", "critique", "wrong with this" | Devil's Advocate | 09-DEVILS_ADVOCATE.md |
| "compare", "choose between", "options" | Comparative Analysis | 10-COMPARATIVE_ANALYSIS.md |
| "trade-off", "giving up", "sacrifice" | Opportunity Cost | 11-OPPORTUNITY_COST.md |
| "explain", "purpose", "why does this exist", "complete picture" | Four Causes | 12-FOUR_CAUSES.md |
| "going through motions", "process theater", "cargo cult", "actually working", "vibe coding" | Cargo Cult Detection | 13-CARGO_CULT_DETECTION.md |
| "how much", "balance", "calibrate", "sweet spot", "too much", "too little", "spectrum" | Golden Mean | 14-GOLDEN_MEAN.md |
Workflow
- Route: Match user keywords to lens using table above
- Load: Read full methodology from
docs/core_principles/[FILE] - Apply: Follow the step-by-step process and use template from that file
If ambiguous, ask:
"Would you like to focus on risks (Pre-Mortem), root cause (5 Whys), or trade-offs (Opportunity Cost)?"
Quick Reference
| Problem Type | Lens |
|---|---|
| Something failed | 5 Whys |
| Planning something risky | Pre-Mortem |
| Choosing between options | Comparative Analysis |
| Understanding a system | Systems Thinking |
| Prioritizing work | Pareto Analysis |
| Understanding why something exists | Four Causes |
| Checking if a practice is actually working | Cargo Cult Detection |
| Finding the right balance/amount | Golden Mean |
| Not sure | Pre-Mortem (safest default) |
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 · 63 lines · 93 tokens per session scan A 6e9b813d8c2c
aod-lens is a skill published in the GitHub repository davidmatousek/agentic-oriented-development-kit (22 stars, last pushed 2mo ago), licensed MIT. It adds 93 tokens to every session and 857 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-lens, 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…