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 skills add neurofoo/agent-skills --skill oodagit clone --depth 1 https://github.com/neurofoo/agent-skillsWrote 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/neurofoo/agent-skills/ooda)<a href="https://agentmods.dev/skills/neurofoo/agent-skills/ooda"><img src="https://agentmods.dev/badge/skills/neurofoo/agent-skills/ooda/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/neurofoo/agent-skills/ooda"><img src="https://agentmods.dev/badge/skills/neurofoo/agent-skills/ooda.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00037 | $0.00838 |
| Opus 5.5 | $0.00015 | $0.00335 |
| Sonnet 5.5 | $0.00007 | $0.00168 |
| Haiku 4.5 | $0.00004 | $0.00084 |
Grade A, and why
ooda 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 1mo 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OODA Loop Analysis
Run a complete OODA loop (Observe, Orient, Decide, Execute) on the problem or decision provided.
Instructions
Work through each phase sequentially. Be thorough but concise.
Phase 1: OBSERVE
Gather facts before analyzing. Ask: "What is actually happening?"
Output:
- Current State: Facts only, no interpretation
- Signals: What prompted this inquiry
- Scope: Boundaries of the situation
- Constraints: Resources, time, rules, dependencies
- Unknowns: Information gaps to acknowledge
Phase 2: ORIENT
Analyze and build understanding. Ask: "Why is this happening?"
Output:
- Root Cause Analysis: Underlying drivers, not just symptoms
- Mental Models: Frameworks that apply (first principles, inversion, second-order effects, etc.)
- Patterns: Similar situations and their outcomes
- Stakeholder Views: How different parties see this
- Assumptions: What we're taking for granted
- Biases: Cognitive traps to watch for
Phase 3: DECIDE
Choose from viable options. Ask: "What's the best approach?"
Output:
- Options (minimum 3):
- Option A — Pros / Cons / Risk level
- Option B — Pros / Cons / Risk level
- Option C — Pros / Cons / Risk level
- Recommendation: Selected approach with rationale
- Success Criteria: How we'll know it worked
- Contingency: Fallback if primary approach fails
Phase 4: EXECUTE
Plan implementation with verification. Ask: "How do we act and confirm?"
Output:
- Action Steps: Ordered, concrete steps
- Verification Points: How to check progress at each stage
- Timeline: Realistic schedule
- First Action: The immediate next step
Feedback Loop
End with:
- Key Risks: What could derail this
- Review Trigger: When to reassess (time or event based)
Format
Use clear headers for each phase. Be direct and actionable. Avoid fluff.
Examples
Business: Product Launch Timing
Context: Feature 85% complete, competitor launching similar feature next month.
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.
- 1mo ago First seen · 93 lines · 37 tokens per session scan A a2eeeae14487
ooda is a skill published in the GitHub repository neurofoo/agent-skills (122 stars, last pushed 9mo ago), licensed MIT. It adds 37 tokens to every session and 838 once invoked, about $0.0001 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…