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 scan-healthgit 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/scan-health)<a href="https://agentmods.dev/skills/mataeil/ooda-loop/scan-health"><img src="https://agentmods.dev/badge/skills/mataeil/ooda-loop/scan-health.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.00028 | $0.02392 |
| Opus 5 | $0.00014 | $0.01196 |
| Sonnet 5 | $0.00006 | $0.00478 |
| Haiku 4.5 | $0.00003 | $0.00239 |
Grade A, and why
scan-health scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -o /dev/null -w "%{http_code} %{time_total}" --max-time <timeout_seconds> <url> How it starts
The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
scan-health: Service Health Monitor
The "eyes" of the harness. Checks configured HTTP endpoints for availability and response time, compares against baseline metrics, and generates alerts when thresholds are breached.
- Checks configured HTTP endpoints for availability and response time
- Compares against baseline metrics stored in service_health.json
- Generates alerts when thresholds are breached
- READ-ONLY: no code changes, no PRs — writes only to agent/state/service_health.json
Safety Rules
- HALT file — Check
config.safety.halt_filebefore any work. If present, print reason and stop. - Read-only — Only writes to
agent/state/service_health.json. No external API modifications. - Graceful degradation — Record failures without crashing. Missing config → skip with a message.
Step 0: Safety
Check the HALT file at config.safety.halt_file. If it exists, print:
HALT: <reason>. scan-health aborted. and exit.
Check config.health_endpoints. If missing or empty:
No health endpoints configured. Skipping. — exit 0.
Validate the list before proceeding:
- Deduplicate — remove duplicate URLs (keep first occurrence).
- Reject malformed URLs — entries that do not start with
http://orhttps://are skipped with a warning:[WARN] Skipping malformed URL: <url>. - Cap at 20 endpoints — if more than 20 remain after dedup, check only the first 20 and warn:
[WARN] Endpoint list truncated to 20 (had <N>).
Step 0.5: Lens Load (Adaptive Context)
Read agent/state/service_health/lens.json. If missing or unparseable, proceed
with base behavior only — this step is purely additive.
If lens exists:
- focus_items (confidence >= 0.6): Prioritize these endpoints/metrics first. Allocate extra time and retries to high-priority items.
- learned_thresholds (confidence >= 0.6): Override default thresholds. For example, if the lens says endpoint X has a learned threshold of 800ms instead of the default 1500ms, use 800ms for anomaly detection on that endpoint.
- discovered_signals (actionable=true): Include these as additional diagnostic checks beyond the base behavior. For example, if the lens says "deploy failures correlate with health degradation", check recent deploy status first.
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 · 236 lines · 28 tokens per session scan A 6af168c7dc6e
scan-health is a skill published in the GitHub repository mataeil/OODA-loop (5 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 2,392 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
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…
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…
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…
write-plan
Use in the Plan phase after the spec is approved - dispatches the planner agent to draft the executable plan from the standard template (decision summary, T-xxx task breakdown with test-first + verify per task), gets the user's approval, records the plan (opening the write gate), and mirrors the breakdown into Claude…
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…