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 imisic/claude-marketplacenpx agentmods add plugins/imisic/claude-marketplace/dev-loopgit clone --depth 1 https://github.com/imisic/claude-marketplaceGrade 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 2d 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",
"description": "The everyday dev loop as three stack-neutral commands: fix debugs a bug or batch-applies a review report by severity, commit runs pre-flight checks and drafts a conventional message behind a sensitive-file gate, ship chains review, fix, and commit with a gate between each phase.",
"version": "1.2.0",
"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",
"workflow"
]
}
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.
- 2d ago First seen · 20 lines scan A b4d239a8462c
dev-loop is a plugin published in the GitHub repository imisic/claude-marketplace (2 stars, last pushed 20d 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
open-pr
Pre-flight checks and PR creation workflow: run tests, open a PR, code review, and check CI.
gates
Four stateless PreToolUse gates, a PostToolUse JSON-config guard, and a docs-consolidation trigger. Denies a git commit that changes code without staging its covering docs (per-plugin README/CLAUDE.md pairs, or the nearest README/CLAUDE/AGENTS walking up); asks before a new-project scaffold command (npm create vite…
axiom-git
Composes Conventional Commits messages with gitmoji from the staged diff, deciding type, scope, emoji, subject, and body, and gating on protected branches, staged secrets, and pre-commit hooks.
fakoli-crew
Nine specialist AI agents for software engineering — generalist roles (polyglot architect, code reviewer, security auditor, researcher, plugin engineer, integration specialist, documentation writer, infrastructure keeper, QA validator) with TDD enforcement, systematic debugging, and verification gates. Plugin-surface…
fakoli-plugin-critic
Five specialist critic agents for Claude Code plugin development — agent-critic (frontmatter/color/tools), skill-critic (lazy-loading/no-fuzzy-detection), hook-critic (contract-aware/${CLAUDEPLUGINROOT}), mcp-critic (schema/actor-validation), structure-critic (manifest/CHANGELOG/version-sync). Audit any plugin (your.
anvil-pulse
Live operator dashboard for long autonomous anvil runs: claims, phases, lease countdowns, event feed, and stuck-state detection served as a local web page, plus an optional Claude Code statusline segment.