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 minimal-domain-skillgit 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/minimal-domain-skill)<a href="https://agentmods.dev/skills/mataeil/ooda-loop/minimal-domain-skill"><img src="https://agentmods.dev/badge/skills/mataeil/ooda-loop/minimal-domain-skill.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.00029 | $0.00559 |
| Opus 5 | $0.00015 | $0.00280 |
| Sonnet 5 | $0.00006 | $0.00112 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
scan-disk 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 6d 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.
What it actually says
/scan-disk — Minimal Domain Skill Example
The smallest useful Observe skill: it reads disk usage, records a baseline, and emits an alert when usage crosses a learned threshold. Use it as a 30-line template for your own domain. Every skill starts with a HALT check.
Step 0: Safety
ls agent/safety/HALT 2>/dev/null && echo "HALT_ACTIVE" || echo "HALT_INACTIVE"
If HALT is active, print the reason and stop immediately.
Step 1: Observe
df -P / | tail -1 | awk '{print $5}' | tr -d '%' # → integer percent used
Load the lens (agent/state/disk_usage/lens.json) if present. Use its
learned_thresholds for warn_pct if it has one; otherwise default warn_pct = 85.
Step 2: Record + alert
Write agent/state/disk_usage/state.json:
{
"schema_version": "1.0.0",
"last_run": "<now ISO-8601>",
"status": "healthy", // healthy | degraded | critical
"metrics": { "used_pct": 73 },
"alerts": [] // e.g. ["disk 91% > warn_pct 85"] when crossed
}
Set status: "degraded" and add an alert when used_pct >= warn_pct;
"critical" at >= 95. The evolve engine reads status/alerts during Observe
and factors them into scoring.
Adaptive Lens (optional but recommended)
evolve's Step 5-E initializes and updates agent/state/disk_usage/lens.json
automatically. To participate, just emit consistent metrics/alerts; the engine
learns a per-host warn_pct over time (raising it on repeated false positives,
lowering it after real incidents). You don't write the lens yourself.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 71 lines · 29 tokens per session scan A 393a4a5699d4
scan-disk is a skill published in the GitHub repository mataeil/OODA-loop (5 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 559 once invoked, about $0.0001 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
hns-lsel-curator
Local Self-Evolution Loop (LSEL) curator — the CLUSTER + drain engine for the GOOS-local PROPOSE→APPLY seam closure (SPEC-LSEL-LOCAL-EVOLUTION-001). Companion-offset drain of .moai/lessons-inbox.jsonl with a drain-side severity filter that drops the 65% Bash-timeout/sandbox noise, eventkey clustering with a frequency…
moai-domain-svg-infographic
Author editable SVG technical infographics — architecture, flow, comparison, hierarchy — by computing the layout numerically before writing markup, then rendering a 2x PNG via headless Chromium. Carries a CJK-first font stack, a deterministic source lint, and mermaid-vs-SVG selection rules.
moai-foundation-core
Provides MoAI-ADK foundational principles including TRUST 5 quality framework, SPEC-First DDD methodology, delegation patterns, progressive disclosure, agent catalog reference, and token budget management (absorbed from moai-foundation-context). Use when referencing TRUST 5 gates, SPEC workflow, or context window…
moai-workflow-spec
SPEC workflow orchestration with EARS format requirements, acceptance criteria, and Plan-Run-Sync integration for MoAI-ADK development. Use when creating SPEC documents or defining acceptance criteria.
moai-workflow-ddd
Domain-Driven Development workflow specialist using ANALYZE-PRESERVE-IMPROVE cycle for behavior-preserving code transformation. Use when refactoring legacy code or reducing technical debt safely.
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.