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.
npx agentmods add skills/zate/cc-plugins/devloopnpx skills add Zate/cc-plugins --skill devloopgit clone --depth 1 https://github.com/Zate/cc-pluginsWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00010 | $0.02115 |
| Opus 5 | $0.00005 | $0.01058 |
| Sonnet 5 | $0.00002 | $0.00423 |
| Haiku 4.5 | $0.00001 | $0.00212 |
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.
How it starts
The opening of the file, as written. The whole thing — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Devloop - Smart Development Workflow
The main entry point for devloop. Detects your current state and suggests the most relevant actions. You do the work directly.
Step 1: Detect State
Run the state detection script:
"${CLAUDE_PLUGIN_ROOT}/scripts/check-devloop-state.sh"
Parse the JSON output:
state: Current state identifierpriority: 1-7 (lower = more urgent)details: State-specific informationsuggestions: Recommended actions
Step 2: Display Status and Options
Based on detected state, display status and present contextual options:
State: not_setup (Priority 1)
Devloop not set up in this project.
The .devloop/ directory doesn't exist yet.
AskUserQuestion:
questions:
- question: "What would you like to do?"
header: "Setup"
multiSelect: false
options:
- label: "Create a plan (Recommended)"
description: "Autonomous exploration -> actionable plan"
- label: "Deep exploration"
description: "Comprehensive investigation with spike report"
- label: "Quick task"
description: "Small, well-defined fix or change"
- label: "GitHub issues"
description: "Start from an existing issue"
Routing:
- "Create a plan" ->
/devloop:plan $ARGUMENTS - "Deep exploration" ->
/devloop:plan --deep $ARGUMENTS - "Quick task" ->
/devloop:plan --quick $ARGUMENTS - "GitHub issues" ->
/devloop:issues
State: active_plan (Priority 2)
Display plan status from details:
Active Plan: [plan_title]
Progress: [done]/[total] tasks ([pending] remaining)
Next: [next_task]
AskUserQuestion:
questions:
- question: "What would you like to do?"
header: "Action"
multiSelect: false
options:
- label: "Continue working (Recommended)"
description: "Pick up where you left off"
- label: "Ship progress"
description: "Commit and optionally create PR"
- label: "View full plan"
description: "Review the complete plan"
- label: "Start fresh"
description: "Archive current plan and start new"
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 · 291 lines · 10 tokens per session scan A 896bd15cf623
devloop is a skill published in the GitHub repository Zate/cc-plugins (10 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 2,115 once invoked, about $0.0001 per session on Opus 5. 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…