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 agentmods add skills/mataeil/ooda-loop/evolvenpx skills add mataeil/OODA-loop --skill evolvegit clone --depth 1 https://github.com/mataeil/OODA-loopWhat 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 | $0.00050 | $0.35724 |
| Opus 5 | $0.00025 | $0.17862 |
| Sonnet 5 | $0.00010 | $0.07145 |
| Haiku 4.5 | $0.00005 | $0.03572 |
Grade A, and why
evolve 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 2d 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 — 2,922 lines — stays where its author put it; the contents beside it link to each section on GitHub.
evolve: OODA Meta-Orchestrator -- Autonomous Decision Engine
evolve is the brain of OODA-loop. It sits above every domain skill and runs one full OODA loop per cycle: Observe the world, Orient by analyzing patterns and updating beliefs, Decide which domain needs attention most, then Act by invoking the winning skill.
This is NOT a round-robin scheduler. The Orient step differentiates evolve from a cron job -- each cycle it reviews PR outcomes, updates confidence, applies memos, detects urgent signals, and adjusts its world model. Over time it learns which domains produce value and which waste cycles.
Based on John Boyd's OODA loop with an added Reflect step that extracts skill
gaps, writes memos, and feeds the next Orient -- creating a double-loop learning
system. All behavior is driven by config.json. No domain names, skills, or
routing tables are hardcoded.
Safety Rules
These rules are absolute. Violating any is a bug.
- HALT File -- Before ANY work, check
config.safety.halt_file. If it exists, print reason and stop immediately. - Protected Paths -- PRs touching
config.safety.protected_pathsMUST be Risk Tier 3 (human review). No auto-merge ever. - PR Limit -- Max
config.safety.max_prs_per_cyclePRs per cycle (default 1). - State-Only Direct Write -- evolve writes only to
agent/state/evolve/*. All other changes require branch + PR. - Skill Allowlist -- Only invoke skills in
config.safety.skill_allowlist. Unlisted skill = safety violation, skip to Reflect. - PR Size Limits -- Respect
config.safety.max_files_per_pr(20) andconfig.safety.max_lines_per_pr(500). Exceeding = Level 3.
File Structure
agent/state/evolve/
state.json -- cycle_count, last_cycle, decision_log (max 20)
confidence.json -- per-domain confidence scores (0.1-1.0)
goals.json -- user-defined goals with progress tracking
skill_gaps.json -- detected missing capabilities with frequency
memos.json -- cross-cycle notes and score_adjustments
action_queue.json -- RICE-scored pending/in_progress/completed actions
metrics.json -- permanent counters (cycles, PRs, costs)
cost_ledger.json -- daily API cost tracking (resets at 00:00 UTC)
episodes.json -- weekly summaries (tier 2 memory)
principles.json -- permanent learnings (tier 3 memory)
CHANGELOG.md -- cycle activity log (most recent 50)
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.
- 2d ago First seen · 2,922 lines · 50 tokens per session scan A dc9c5ad8597f
evolve is a skill published in the GitHub repository mataeil/OODA-loop (5 stars, last pushed 2mo ago), licensed MIT. It adds 50 tokens to every session and 35,724 once invoked, about $0.0003 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
paper-illustration
Generate publication-quality AI illustrations for academic papers using Gemini image generation. Creates architecture diagrams, method illustrations with Claude-supervised iterative refinement loop. Use when user says "生成图表", "画架构图", "AI绘图", "paper illustration", "generate diagram", or needs visual figures for papers.
overleaf-sync
Two-way sync between a local paper directory and an Overleaf project, so ARIS audit/edit workflows stay on the local copy while collaborators edit in the Overleaf web UI. Use when user says "同步 overleaf", "overleaf sync", "推送到 overleaf", "connect overleaf", "Overleaf 桥接", "pull overleaf", "push overleaf", or wants to…
flow-next-resolve-pr
Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
moai-ref-ui-polish
UI polish and interface-completion reference: the small visual details — concentric border radius, optical alignment, shadow-vs-border, motion easing, typography smoothing, tabular numbers, icon stroke weight, hit areas — that separate polished interfaces from generic ones. Agent-extending skill that amplifies…
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…