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 mataeil/OODA-loop --skill ooda-statusgit clone --depth 1 https://github.com/mataeil/OODA-loopWrote 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/mataeil/ooda-loop/ooda-status)<a href="https://agentmods.dev/skills/mataeil/ooda-loop/ooda-status"><img src="https://agentmods.dev/badge/skills/mataeil/ooda-loop/ooda-status.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.00030 | $0.03945 |
| Opus 5 | $0.00015 | $0.01972 |
| Sonnet 5 | $0.00006 | $0.00789 |
| Haiku 4.5 | $0.00003 | $0.00394 |
Grade A, and why
ooda-status 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 — 332 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ooda-status — Status Dashboard
Display the current state of the OODA-loop at a glance.
Step 0: Safety Check
Check for the HALT file before anything else.
ls agent/safety/HALT 2>/dev/null && echo "HALT_ACTIVE" || echo "HALT_INACTIVE"
If HALT exists, continue rendering the dashboard but mark HALT status as "ACTIVE". Do not abort — status must always be readable regardless of HALT state.
Step 1: Gather Data
Read each file below. If a file is missing, note it and use a safe default value.
If a file exists but contains invalid JSON (parse error), treat it the same as missing
and append an alert: [WARN] Corrupt state file: <path> — skipped (parse error).
Do not let a single corrupt file abort the entire dashboard.
config.json — project name, current level, cost limit, domain list, domain status fields
cat config.json 2>/dev/null || echo "MISSING"
Also read config.mission (the project's purpose the loop drives toward) and each domain's mission_alignment.
Read each domain's status field from config.json to identify which domains are "available" (not yet configured) vs "active" vs "disabled".
agent/state/evolve/state.json — cycle_count, last_cycle timestamp
cat agent/state/evolve/state.json 2>/dev/null || echo "MISSING"
agent/state/evolve/confidence.json — per-domain confidence scores (0.0–1.0)
cat agent/state/evolve/confidence.json 2>/dev/null || echo "MISSING"
agent/state/evolve/action_queue.json — pending and proposed action counts, top action
cat agent/state/evolve/action_queue.json 2>/dev/null || echo "MISSING"
agent/state/evolve/metrics.json — execution counters/streaks (under counters)
cat agent/state/evolve/metrics.json 2>/dev/null || echo "MISSING"
Cost source: today's spend comes from agent/state/evolve/cost_ledger.json
(total_estimated_usd, after confirming date == today UTC; stale date ⇒ $0.00
pending reset) and the limit from config.cost.daily_limit_usd. metrics.json has
NO cost fields — never read cost from it.
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 · 332 lines · 30 tokens per session scan A f13088b942a7
ooda-status is a skill published in the GitHub repository mataeil/OODA-loop (5 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 3,945 once invoked, about $0.0002 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
implement
Use in the Implement phase whenever writing or editing production Java code, or fixing a bug, in a Spring/Spring Boot project. Enforces test-first (red-green-refactor), executes the approved plan step by step, and honors the project's path-scoped tech-stack rules and the task's enforcement set. Preloaded into…
review
Use in the Review phase before claiming any Java/Spring task is complete, fixed, or passing. Spawns the auditor subagents that check the implementation against every applicable skill, rule, and memory item, runs the test suite for fresh evidence, and re-spawns for at most two fix rounds before reporting what survives.…
claudehut-workflow
Use at the start of every session and whenever beginning a coding task in a Java/Spring backend - establishes the ClaudeHut 7-phase agentic workflow, the complexity-tier routing that lets small tasks skip deliberation phases, and the laws that govern which skills and rules must fire. Injected at session start; also…
discover
Use as the FIRST phase of EVERY coding task, before brainstorming - grounds the work in the existing codebase (entry points, key types, structure) and proves whether something reusable already exists. Produces the reuse-scan artifact the write gate requires and the reuse DECISION (adopt / extend / new). Runs inline on…
brainstorm
Use to generate and weigh solution approaches for a problem, after discovery has grounded the context. Produces two or more genuinely distinct options scored on trade-offs, recommends one, and (for code tasks) assembles the enforcement set the rest of the workflow audits against. General-purpose ideation — works for…
capture-learnings
Use in the Learn phase at the end of every task, before declaring done - dispatches the learner agent to record what was learned (conventions, pitfalls, reuse points, decisions) to the cross-session store and refresh the committed memory index, then closes the phase. Runs inline on the main thread (it owns the state…