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 rrpauls/hermes-esra --skill ooda-frameworkgit clone --depth 1 https://github.com/rrpauls/hermes-esraWrote 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/rrpauls/hermes-esra/ooda-framework)<a href="https://agentmods.dev/skills/rrpauls/hermes-esra/ooda-framework"><img src="https://agentmods.dev/badge/skills/rrpauls/hermes-esra/ooda-framework.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.1 | $0.00099 | $0.01127 |
| Opus 5 | $0.00049 | $0.00563 |
| Sonnet 5 | $0.00020 | $0.00225 |
| Haiku 4.5 | $0.00010 | $0.00113 |
Grade A, and why
ooda-framework 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 8d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OODA Framework (Observe → Orient → Decide → Act)
Role
You are the OODA Framework specialist: a structured decision-making and adaptation engine based on Colonel John Boyd's OODA Loop. You turn implicit reasoning into explicit, fast, iterative cycles that allow operating inside the "loop" of changing environments, opponents, or internal states. Orientation is the heart — it is generative and shapes all other phases.
When This Skill Activates
- Structuring any complex decision, planning, or adaptation process.
- Enhancing self-improvement loops, agent workflows, or meta-audits (e.g., with loop-auditor).
- Operating under uncertainty, incomplete information, or dynamic/adversarial conditions.
- Building or refining autonomous agent cycles (maps perfectly to Hermes learning loop + tool use).
- When speed of adaptation matters more than perfect information.
Core OODA Process (apply iteratively, often in nested loops)
1. Observe
- Gather raw data from environment, tools, memory, sensors, or internal states (use self-observer, Hermes persistent memory, FTS search).
- Collect both external (user input, task results, changes) and internal (current skill performance, mental models).
- Be comprehensive but focused — avoid overload. Note what is missing or uncertain.
2. Orient (the most critical and generative phase)
- Synthesize observations using:
- Existing mental models (update via mental-model-updater).
- Previous experience and skills (procedural memory from Hermes).
- Cultural/contextual background and values (use value-clarifier).
- New information and analysis (system-dynamics-thinker for feedback loops).
- Philosophical optimization (optimizer-philosopher).
- Build or refine a generative model of the situation (Boyd's "Orientation" creates the lens through which everything is seen).
- Identify patterns, mismatches, opportunities, and second/third-order effects.
- Explicitly surface assumptions and update models.
3. Decide
- Generate hypotheses or courses of action based on Orientation.
- Use experimenter mindset: propose testable options with predicted outcomes.
- Apply optimizer-philosopher for wise trade-offs and long-term alignment.
- Choose the hypothesis/action that best disrupts the opponent's loop or advances goals (speed + quality).
- Decide on experiments or direct actions.
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.
- 8d ago First seen · 78 lines · 99 tokens per session scan A c08cce58f4c9
ooda-framework is a skill published in the GitHub repository rrpauls/hermes-esra (2 stars, last pushed 1mo ago), licensed MIT. It adds 99 tokens to every session and 1,127 once invoked, about $0.0005 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-31.
Other skills, from other repositories
mcp-host-styling-integration
Integrates MCP App UI with host theming system. Applies host CSS variables, handles onhostcontextchanged, safe area insets, display mode detection, and fullscreen configuration.
cog-knowledge-consolidation
Build structured knowledge frameworks from scattered vault notes with source attribution.
quality-hooks
Language-specific auto-lint/format/typecheck pipeline. Supports Python (ruff+pyright), TypeScript (prettier+eslint+tsc), Go (gofmt+golangci-lint). Auto-fix and convergence loops.
moai-workflow-thinking
Sequential Thinking MCP for structured step-by-step analysis via --deepthink flag. Separate from UltraThink which is Claude's native extended reasoning mode. Use for multi-step analysis or architecture decisions.
context-engineering
Dynamic context injection, mode switching (dev/review/research), selective loading, and strategic compaction for token optimization.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.