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/dev-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/plugins/choiyounggi/dev-loop/dev-loop)<a href="https://agentmods.dev/plugins/choiyounggi/dev-loop/dev-loop"><img src="https://agentmods.dev/badge/plugins/choiyounggi/dev-loop/dev-loop/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/dev-loop/dev-loop"><img src="https://agentmods.dev/badge/plugins/choiyounggi/dev-loop/dev-loop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
dev-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
{
"name": "dev-loop",
"displayName": "dev-loop",
"description": "Multi-agent orchestration grounded in an LLM wiki. /dev-loop:orchestrate splits one goal into a dependency graph of parallel Claude Code sessions, each in its own worktree, and supervises them natively on Orca (a tracked Task + Dispatch per phase, pushed worker_done / question / escalation events instead of polling, stall detection; raw tmux fallback). Every plan decision must cite a page in a bundled best-practice wiki of 400+ pages across 10 domains, checked by machine gates and a fresh-context plan reviewer, and verified insights from your sessions return as reviewed wiki PRs.",
"version": "1.33.0",
"author": {
"name": "choiyounggi",
"url": "https://github.com/choiyounggi"
},
"homepage": "https://github.com/choiyounggi/dev-loop",
"license": "MIT",
"repository": "https://github.com/choiyounggi/dev-loop",
"icon": "./assets/icon.png",
"keywords": ["orchestration", "multi-agent", "parallel-agents", "orca", "tmux", "worktree", "llm-wiki", "planning", "tdd", "knowledge-base"]
}
What it installs
The manifest is a name and a version. 9 skills, 11 agents, 6 hooks, 1 MCP server travel with it, and installing the plugin installs all of them — 1,395 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill loop-implement A 94 tokens
- Skill wiki-plan A 62 tokens
- Skill knowledge-flush A 117 tokens
- Skill configure A 128 tokens
- Skill graph-setup A 106 tokens
- Skill wiki-lint A 103 tokens
- Skill wiki-ingest A 58 tokens
- Skill wiki-query A 49 tokens
- Skill orchestrate D 71 tokens
- Agent task-planner-r1 A 0 tokens
- Agent task-planner A 0 tokens
- Agent task-analyst-r1 A 0 tokens
- Agent integration-reviewer A 81 tokens
- Agent integration-reviewer-r1 A 106 tokens
- Agent plan-reviewer A 32 tokens
- Agent test-quality-auditor A 88 tokens
- Agent test-quality-auditor-r1 A 115 tokens
- Agent task-reviewer A 80 tokens
- Agent task-reviewer-r1 A 105 tokens
- Agent task-analyst A 0 tokens
- Hook Notification A not measured
- Hook PreToolUse A not measured
- Hook StopFailure A not measured
- Hook Stop A not measured
- Hook SessionStart A not measured
- Hook UserPromptSubmit A not measured
- MCP server dev-loop-wiki A not measured
What ships with it
1 file beside plugin.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 Changed 986e7f91f67c
- 2d ago Changed 612e29138734
- 5d ago Changed 2a964834f336
- 6d ago Changed · +4 lines e8e0d2074d6f
- 7d ago Changed a174d137c0dc
- 10d ago Changed 1fcb94a98c64
- 16d ago Changed ab6b2551a622
- 19d ago Changed e4c6999f47e6
- 24d ago Changed 14cd2e31081c
- 28d ago First seen · 12 lines scan A f86889691fce
dev-loop is a plugin published in the GitHub repository choiyounggi/dev-loop (6 stars, last pushed yesterday), 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
atdd
Acceptance Test Driven Development for Claude Code. Enforces the ATDD methodology: write Given/When/Then specs first, generate a project-specific test pipeline, maintain two test streams (acceptance + unit). Inspired by Robert C. Martin's acceptance test approach from empire-2025.
hcf
Autonomous development orchestration with parallel TDD execution.
flow
Skill-driven workflow plugin for GitHub development with excellence-by-default quality gates. Encodes team knowledge as composable skills, enforces safety through hooks, and compounds learning across sessions. Strict TDD, Stranger Test, holdout validation, and evidence-based verification built in. Durable goals…
superpowers-orchestrator
Agentic development framework for Claude Code — disciplined workflow routing, TDD enforcement, safety hooks, systematic debugging, and code review.
harnessay
Profile Claude Code and Codex transcripts: context budget reports, before/after comparisons, source evidence, and skill regression tests. Local-only, stdlib-only.
engineering-practices
Git commits, conventional releases, refactoring, test-driven development, and engineering ways of working skills.