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/helpnpx skills add Zate/cc-plugins --skill helpgit 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.00019 | $0.02308 |
| Opus 5 | $0.00010 | $0.01154 |
| Sonnet 5 | $0.00004 | $0.00462 |
| Haiku 4.5 | $0.00002 | $0.00231 |
Grade C, and why
help scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .devloop/ && /devloop How it starts
The opening of the file, as written. The whole thing — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Devloop Help
Interactive guide to devloop.
Step 1: Choose Topic
If $ARGUMENTS specifies a topic, skip to that section. Otherwise:
AskUserQuestion:
questions:
- question: "What would you like to learn about?"
header: "Topic"
multiSelect: false
options:
- label: "Getting Started"
description: "New to devloop? Start here"
- label: "Commands"
description: "What each command does"
- label: "The Loop"
description: "The plan -> run -> fresh cycle"
- label: "Skills & Agents"
description: "On-demand knowledge and parallel work"
- label: "Superpowers"
description: "How devloop works with superpowers plugin"
Topic: Getting Started
What is devloop?
Development workflow where Claude does the work directly. No routine agents. Just you, Claude, and the code.
Quick Start
/devloop:plan "How should we implement feature X?" # Plan (or --deep for exploration)
/devloop:run # Execute tasks
/devloop:fresh && /clear # Save state, clear context (every fresh_threshold tasks (default 10, configurable in .devloop/local.md))
/devloop:run # Continue execution
First Session
- Have a task?
/devloop:plan [task](or--deepfor detailed exploration) - Claude explores, creates plan
- You approve
/devloop:runto implement- Every fresh_threshold tasks (default 10, configurable in .devloop/local.md):
/devloop:freshthen/clearthen/devloop:run - Done?
/devloop:ship
Topic: Commands
Decision Tree
Starting new work?
|-- Unclear requirements -> /devloop:plan --deep
|-- Small, clear task -> /devloop:plan --quick
|-- Normal feature -> /devloop:plan
|-- Have a plan -> /devloop:run
Mid-workflow?
|-- Context heavy -> /devloop:fresh -> /clear -> /devloop:run
|-- Ready to commit -> /devloop:ship
|-- Want review -> /devloop:review
Returning?
|-- /devloop:run
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 · 302 lines · 19 tokens per session scan C 5441fec2a69d
help is a skill published in the GitHub repository Zate/cc-plugins (10 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 2,308 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). 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…