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/imisic/claude-marketplaceWrote 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/imisic/claude-marketplace/dev-loop)<a href="https://agentmods.dev/plugins/imisic/claude-marketplace/dev-loop"><img src="https://agentmods.dev/badge/plugins/imisic/claude-marketplace/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/imisic/claude-marketplace/dev-loop"><img src="https://agentmods.dev/badge/plugins/imisic/claude-marketplace/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 5d 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
{
"name": "dev-loop",
"displayName": "Dev Loop: Fix, Commit and Ship",
"description": "Three commands for the daily loop in Claude Code: fix a bug or apply a review report, commit with pre-flight checks, or run review, fix and commit as one flow, pausing after the review for your go-ahead.",
"version": "1.3.2",
"author": {
"name": "Ivan Misic",
"url": "https://ivanmisic.net"
},
"homepage": "https://ivanmisic.net/toolshed/plugins/dev-loop",
"repository": "https://github.com/imisic/claude-marketplace",
"license": "MIT",
"keywords": [
"git",
"commit",
"conventional-commits",
"code-review",
"debugging",
"bug-fixing",
"developer-workflow"
],
"documentationUrl": "https://github.com/imisic/claude-marketplace/tree/main/plugins/dev-loop#readme",
"privacyPolicyUrl": "https://github.com/imisic/claude-marketplace/tree/main/plugins/dev-loop#privacy",
"supportUrl": "https://github.com/imisic/claude-marketplace/issues",
"termsOfServiceUrl": "https://github.com/imisic/claude-marketplace/blob/main/LICENSE"
}
What it installs
The manifest is a name and a version. 3 skills travel with it, and installing the plugin installs all of them — 63 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 5d ago Changed 9f36556ca522
- 12d ago Changed · +7 lines 41ea14eebcfe
- 1mo ago First seen · 20 lines scan A b4d239a8462c
dev-loop is a plugin published in the GitHub repository imisic/claude-marketplace (1 stars, last pushed today), 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
developer-essentials
Essential developer skills including Git workflows, SQL optimization, error handling, code review, E2E testing, authentication, debugging, and monorepo management.
pipecat-dev
Development workflow skills for contributing to the Pipecat project.
fix-all
Run bin/claude-review --print and automatically fix all reported issues, committing each fix individually.
han-github
Github specific extensions to the Han plugin for agentic planning and coding. Provides skills to post code reviews as PR comments, update a PR description with a consistent format, etc.
git-pr-workflows
Git workflow automation, pull request enhancement, and team onboarding processes.
odin-git
ODIN workflows for commits, branches, pull requests, review feedback, and issue tracking.