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/plannpx skills add Zate/cc-plugins --skill plangit 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.00014 | $0.01233 |
| Opus 5 | $0.00007 | $0.00616 |
| Sonnet 5 | $0.00003 | $0.00247 |
| Haiku 4.5 | $0.00001 | $0.00123 |
Grade A, and why
plan 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Devloop Plan
Create actionable plan from topic. Do the work directly.
Bash hygiene: prefer quiet flags to minimize output (npm install --silent, git status -sb, pipe long output through | tail -n 20).
Step 1: Parse Input
Extract topic from $ARGUMENTS. If missing, show usage: /devloop:plan <topic> [--deep|--quick|--from-issue N].
If --from-issue N: Fetch with gh issue view $N --json number,title,body,url. Use title as topic, body as context.
Step 2: Check Existing Plan (Silent)
If .devloop/plan.md exists:
- Count tasks (no file read needed):
done=$(grep -cE "^\s*- \[x\]" .devloop/plan.md 2>/dev/null || echo 0) total=$(grep -cE "^\s*- \[[ x~!-]\]" .devloop/plan.md 2>/dev/null || echo 0) - If
done == totalandtotal > 0: auto-archive silently:"${CLAUDE_PLUGIN_ROOT}/scripts/archive-plan.sh" .devloop/plan.md --force - If incomplete (
done < total): prompt to archive (force) or cancel. - If no plan file or
total == 0: continue to Step 3.
Step 3: Route by Mode
If --quick: Fast Path
Use for bug fixes with known cause or small additions.
- Create todo list (2-4 tasks).
- If too complex, suggest removing
--quick. - Implement directly: Read (3-5 files), Write/Edit, test, summarize.
- STOP after completion.
If --deep: Comprehensive Exploration
Use for unclear requirements or architectural changes.
- Define Scope: Detect spike type (Tech decision, New feature, Risk, etc.).
- AskUserQuestion: User selects aspects (Feasibility, Scope, Risk, Dependencies, Approach, Effort, Impact).
- Research: Explore 8-10 files.
- Evaluate: Provide verdict per aspect (Confidence, Blockers, Size, Hours/Days).
- Write Report: Save to
.devloop/spikes/{topic}.md. - Display Summary: Show direct answer, recommendation, and findings.
- Proceed to Step 4.
Default Mode: Autonomous Planning (Steps 4-7)
Step 4: Context Detection (Silent)
Run ${CLAUDE_PLUGIN_ROOT}/scripts/check-devloop-state.sh. Detect tech stack and patterns from CLAUDE.md.
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 · 104 lines · 14 tokens per session scan A 7b9a249c8218
plan is a skill published in the GitHub repository Zate/cc-plugins (10 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 1,233 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…