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.
git clone --depth 1 https://github.com/choiyounggi/loop-orchestratorWrote 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/plugins/choiyounggi/loop-orchestrator/marketplace)<a href="https://agentmods.dev/plugins/choiyounggi/loop-orchestrator/marketplace"><img src="https://agentmods.dev/badge/plugins/choiyounggi/loop-orchestrator/marketplace/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/plugins/choiyounggi/loop-orchestrator/marketplace"><img src="https://agentmods.dev/badge/plugins/choiyounggi/loop-orchestrator/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
loop-orchestrator marketplace 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.
What it actually says
{
"$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
"name": "loop-orchestrator",
"description": "Marketplace for loop-orchestrator — a methodology-grounded multi-session orchestrator plugin for Claude Code.",
"owner": {
"name": "choiyounggi",
"url": "https://github.com/choiyounggi"
},
"plugins": [
{
"name": "loop-orchestrator",
"description": "Orchestrate one natural-language goal into parallel tmux Claude Code sessions — decompose, plan, implement, verify, and merge through a methodology-grounded loop (TDD / PDCA / Reflexion). Gated where it matters: task-split approval and pre-merge review.",
"category": "development",
"author": {
"name": "choiyounggi",
"url": "https://github.com/choiyounggi"
},
"source": {
"source": "url",
"url": "https://github.com/choiyounggi/loop-orchestrator.git"
},
"homepage": "https://github.com/choiyounggi/loop-orchestrator",
"version": "0.6.0",
"tags": [
"orchestrator",
"multi-agent",
"tmux",
"worktree",
"verification-loop",
"tdd",
"claude-code"
]
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
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.
- 2mo ago First seen · 36 lines scan A 3f0208e947cd
loop-orchestrator marketplace is a plugin published in the GitHub repository choiyounggi/loop-orchestrator (2 stars, last pushed 3mo 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
agent-traffic-control
Coordination toolkit for parallel Claude Code sessions sharing one repo — issue-pickup claim protocol (assignee + wip label), worktree & session-isolation pitfalls, parallel-PR conflict recovery, subagent-integrity edge cases, and squash/merge mechanics for parallel-PR workflows. Plus two opt-in hooks: leg-guard…
plan-cascade
AI-powered cascading development framework with design document system and multi-agent collaboration. Breaks down projects into Features (Mega Plan), Features into Stories (Hybrid Ralph), with auto-generated technical design docs, dependency-driven batch execution, Git Worktree isolation, and support for multiple AI…
orchestrate
Decompose a large goal into a tree of parallel workers running in isolated git worktrees, collect typed handoffs, replan, repeat until terminal. Idiomatic Claude Code realization of Cursor /orchestrate.
dos-kernel
The kernel that doesn't believe the agents. Exposes the DOS trust syscalls as MCP tools — verify what actually shipped (git ancestry, not self-report), arbitrate file-tree collisions before two agents edit the same files, and refuse with a structured reason from a closed vocabulary. Requires the dos-kernel Python…
trustmybot marketplace
Plugin marketplace listing 2 plugins: tmb, tmb-rc.
agent-harness
Multi-agent harness for Claude Code: Planner→Generator→Evaluator sprints executed as background dynamic workflows (Agent-tool fallback), fable/opus/sonnet/haiku model routing with per-role reasoning effort, harness-engineering framework for design/diagnosis, and Anthropic 2026-04-04 P-G-E pattern.