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-configgit 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-config)<a href="https://agentmods.dev/skills/mataeil/ooda-loop/ooda-config"><img src="https://agentmods.dev/badge/skills/mataeil/ooda-loop/ooda-config/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/mataeil/ooda-loop/ooda-config"><img src="https://agentmods.dev/badge/skills/mataeil/ooda-loop/ooda-config.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.00016 | $0.04757 |
| Opus 5.5 | $0.00006 | $0.01903 |
| Sonnet 5.5 | $0.00003 | $0.00951 |
| Haiku 4.5 | $0.00002 | $0.00476 |
Grade A, and why
ooda-config 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 2mo 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 — 439 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ooda-config: Configuration Management CLI
View, modify, and validate config.json without editing JSON by hand.
All writes: back up to config.json.bak, then re-parse to confirm valid JSON.
Step 0: HALT + Preflight
Read config.safety.halt_file (default agent/safety/HALT).
If that path exists: HALT: <reason>. ooda-config aborted. — stop.
If config.json is missing and subcommand is not validate:
config.json not found. Run /ooda-setup to create one. — stop.
Parse the user's invocation to one of: show | level | domain add | domain remove | domain list | safety | validate | lens review | lens reset | action {list|approve|defer|reject|prioritize} | mode/season | rotation {show|reset} | context show | rollback {cycle} | auto-merge {on|off}.
Unknown subcommand → print the Usage block and exit.
Step A — show
Print a compact summary: schema_version, project fields, domain list with weight/skill/enabled status, current progressive_complexity level and name, and key safety values (halt_file presence, confidence_threshold, max_prs_per_cycle).
Step B — level {N}
- Validate N is 0–3; fail fast otherwise.
- If N == 3, print explicit warning and require a typed confirmation phrase:
Only accept the exact phrase[DANGER] Level 3 enables AUTONOMOUS mode: - The agent autonomously writes code and opens PRs (no prompt). - By DEFAULT those are DRAFT PRs you review and merge — nothing reaches main without your click. (You stay in command.) - Auto-merge is a SEPARATE opt-in: only if you ALSO run `/ooda-config auto-merge on` (safety.enable_auto_merge=true) will it merge LOW-RISK PRs by itself — non-protected paths, <= auto_merge_max_files / auto_merge_max_lines, tests green — with a post-merge health check that auto-reverts + HALTs on failure. It stays OFF until you flip it. - Only the HALT file or the daily cost cap can stop a running cycle. Type "enable autonomous" to confirm (anything else cancels):enable autonomous. Any other response:Cancelled. - Back up config.json.
- Set
progressive_complexity.current_level = Nandimplementation.enabled = (N == 3). - Write + validate JSON. Print:
Level changed: <old> → <N> ("<name>").
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.
- 2mo ago First seen · 439 lines · 16 tokens per session scan A 4c809b813efa
ooda-config is a skill published in the GitHub repository mataeil/OODA-loop (6 stars, last pushed 4mo ago), licensed MIT. It adds 16 tokens to every session and 4,757 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-31.
Other skills, from other repositories
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.
moai-lane-watchdog
One lane stall watchdog iteration: measure lane progress on three channels, classify the stall cause, apply the remedy or resolve the judgment through the decision ladder — instead of waiting on a reply — then record the outcome and report. Reads the unified --auto doctrine at…
principle-outcome-oriented-execution
Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.