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 choiyounggi/dev-loopnpx agentmods add plugins/choiyounggi/dev-loop/marketplacegit clone --depth 1 https://github.com/choiyounggi/dev-loopGrade 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
{
"$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
"name": "dev-loop",
"description": "Marketplace for dev-loop — a wiki-grounded implementation loop plugin for Claude Code (loop-orchestrator + dev-llm-wiki, merged).",
"owner": {
"name": "choiyounggi",
"url": "https://github.com/choiyounggi"
},
"plugins": [
{
"name": "dev-loop",
"description": "loop-orchestrator's verification loop with the plan step fixed to a wiki-grounded planning methodology (wiki-plan) over a bundled semantic-layer wiki, plus a knowledge-capture loop that harvests verified insights and opens reviewed wiki PRs via knowledge-flush.",
"category": "development",
"author": {
"name": "choiyounggi",
"url": "https://github.com/choiyounggi"
},
"source": {
"source": "url",
"url": "https://github.com/choiyounggi/dev-loop.git"
},
"homepage": "https://github.com/choiyounggi/dev-loop",
"version": "1.14.0",
"tags": [
"orchestrator",
"verification-loop",
"tdd",
"wiki",
"planning",
"knowledge-base",
"claude-code"
]
}
]
}
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 · 36 lines scan A aa001f19909d
dev-loop is a plugin published in the GitHub repository choiyounggi/dev-loop (4 stars, last pushed 2d 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-mega-brain
OKF-powered knowledge context for Claude Code — injects your project knowledge base at every session.
flutter-skills
Plugin marketplace listing 1 plugin: flutter.
mozg-stake
Hands for the Stake Engine brain: upload math and front-end bundles, run compliance checks, publish a release. Needs the stakecli binary.
cc-spec-driven
Spec-Driven Document-First Development Framework.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
nextjs
Official Claude Code plugin marketplace for Next.js, serving the skills that ship in the vercel/next.js repository.