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.
/plugin marketplace add mataeil/OODA-loopnpx agentmods add plugins/mataeil/ooda-loop/marketplacegit clone --depth 1 https://github.com/mataeil/OODA-loopGrade A, and why
ooda-loop 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 yesterday.
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
{
"$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
"name": "ooda-loop",
"plugins": [
{
"name": "ooda-loop",
"description": "An autonomous operations layer for your live side project. It watches, re-orients from which PRs you merge and reject, and opens small revertible PRs — bounded by a HALT file, protected paths, and a hard cost cap. Built on Boyd's OODA loop. You stay in command.",
"category": "development",
"author": {
"name": "Taeil Ma",
"url": "https://github.com/mataeil"
},
"source": {
"source": "url",
"url": "https://github.com/mataeil/OODA-loop.git"
},
"homepage": "https://github.com/mataeil/OODA-loop",
"tags": ["ooda-loop", "autonomous-agent", "operations", "side-projects"],
"version": "1.6.1"
}
]
}
What ships with it
1 file beside marketplace.json 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.
- yesterday First seen · 23 lines scan A e9b8964d8100
ooda-loop is a plugin published in the GitHub repository mataeil/OODA-loop (5 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
claude-code-tips
Developer experience essentials: GitHub Actions debugging, conversation half/quarter-cloning, context handoffs, research (Reddit and Hacker News), private GitHub search, and Claude Code version checks.
elisym
elisym plugins for Claude Code - discover, hire, and pay AI agents over Nostr.
the-loop
Plugin marketplace listing 1 plugin: the-loop.
the-loop
An opinionated product-development-lifecycle harness that lets coding agents deliver work items end-to-end, with minimal human intervention, through a predictable loop of plan, execute, self-review, critic-review and escalate.
mappamind-plugins
Grounded, visual architecture-impact cards for AI coding sessions.
agent-levers
Levers for AI coding agents — multiply the agent's force, divide the human's effort.