devloop

A lightweight development workflow plugin built around plans, task execution, fresh-context agents, Git operations, and pull-request feedback. It provides the surrounding process for organizing and completing coding work.

In plain words
What is it for?
Use it to plan changes, run planned tasks, coordinate separate agents, manage Git-related steps, and incorporate pull-request feedback.
Why use it?
It connects planning, implementation, review follow-up, and Git workflow steps into one development process. The input does not specify every command or feature available.

Plugin for Claude Code

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.

Claude Code
/plugin marketplace add Zate/cc-plugins
agentmods
npx agentmods add plugins/zate/cc-plugins/devloop
Clone the repo
git clone --depth 1 https://github.com/Zate/cc-plugins

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

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

plugins/devloop/.claude-plugin/plugin.json · 14 lines

What it actually says

{
  "name": "devloop",
  "version": "3.25.1",
  "description": "Lightweight development workflow with plan/run/fresh pattern, git workflow integration, PR feedback, and autonomous execution. Optimized for efficiency - minimal hooks, on-demand skills, direct execution.",
  "author": {
    "name": "Zate",
    "email": "[email protected]"
  },
  "homepage": "https://github.com/Zate/cc-plugins",
  "repository": "https://github.com/Zate/cc-plugins",
  "license": "MIT",
  "keywords": ["devloop", "workflow", "planning", "development"]
}
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 First seen · 14 lines scan A 296db022d62b

Subscribe to this mod's changes

devloop is a plugin published in the GitHub repository Zate/cc-plugins (10 stars, last pushed 1mo 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.