dev-loop

dev-loop is a plugin for Claude Code from choiyounggi/dev-loop. Its manifest loads nothing; the 9 skills, 11 agents, 6 hooks, 1 MCP server it bundles cost 1,395 tokens per session together, scanned A, original, MIT.

A development workflow plugin that combines repeated verification cycles with a shared project wiki. TDD means writing tests before code; PDCA means repeatedly planning, doing, checking, and adjusting.

In plain words
What is it for?
Planning changes against documented guidance, implementing and checking them in a loop, reviewing failures, and collecting verified lessons for a team wiki.
Why use it?
It gives coding work a fixed planning and review process, while capturing useful findings for later projects instead of leaving them only in chat history.

Plugin for Claude Code

Written for Claude Code: a Claude Code plugin manifest. Also seen: mentions Claude Code.

Good fit Planning changes against documented guidance, implementing and checking them in a loop, reviewing failures, and collecting verified lessons for a team wiki.

Compare 6 plugins from other repositories ↓
Install in Claude Code
/plugin marketplace add choiyounggi/dev-loop
/plugin install dev-loop
Install

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.

Clone the repo
git clone --depth 1 https://github.com/choiyounggi/dev-loop

Made for: Claude Code.

Wrote 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.

agentmods badge for dev-loop

README.md
[![agentmods](https://agentmods.dev/badge/plugins/choiyounggi/dev-loop/dev-loop/github.svg)](https://agentmods.dev/plugins/choiyounggi/dev-loop/dev-loop)
Your own site
<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.

agentmods 80×15 button for dev-loop

Your own site · 80×15
<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>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured The manifest loads nothing itself; its 9 skills, 11 agents, 6 hooks, 1 MCP server cost 1,395 tokens a session between them.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Security

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.

.claude-plugin/plugin.json · 16 lines

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"]
}
Files

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.

Changes

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.

  1. yesterday Changed 986e7f91f67c
  2. 2d ago Changed 612e29138734
  3. 5d ago Changed 2a964834f336
  4. 6d ago Changed · +4 lines e8e0d2074d6f
  5. 7d ago Changed a174d137c0dc
  6. 10d ago Changed 1fcb94a98c64
  7. 16d ago Changed ab6b2551a622
  8. 19d ago Changed e4c6999f47e6
  9. 24d ago Changed 14cd2e31081c
  10. 28d ago First seen · 12 lines scan A f86889691fce

Subscribe to this mod's changes

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.