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/runnpx skills add Zate/cc-plugins --skill rungit 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.00009 | $0.01221 |
| Opus 5 | $0.00005 | $0.00611 |
| Sonnet 5 | $0.00002 | $0.00244 |
| Haiku 4.5 | $0.00001 | $0.00122 |
Grade A, and why
run 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.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Devloop Run
Execute plan tasks autonomously. 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).
Monitor for long commands: Use Monitor (not Bash) for test suites, builds, and full-codebase linting to stream output in real-time. Use Bash for all short commands (git ops, ls, devloop scripts).
Long-running commands that warrant Monitor:
- Test suites:
npm test,pytest,go test ./...,cargo test,make test,jest,vitest,mocha - Builds:
npm run build,make,cargo build,go build,tsc,webpack,vite build,gradle,mvn - Full-codebase linting:
eslint .,ruff check .,pylint src/,golangci-lint run
Monitor pattern (always include failure patterns in the filter):
Monitor({ description: "test run", command: "npm test 2>&1 | grep --line-buffered -E 'PASS|FAIL|Error|passed|failed'", timeout_ms: 300000, persistent: false })
Fallback: if Monitor errors or is unavailable, use Bash directly.
Step 1: Check Plan State
Run ${CLAUDE_PLUGIN_ROOT}/scripts/check-plan-complete.sh .devloop/plan.md.
- No plan: Show entry points (
/devloop:plan) and STOP. - Complete: AskUserQuestion: Ship it, Archive, or Review. STOP.
- Pending: Continue to Step 2.
Step 2: Parse Arguments
--max-iterations N: Default 50.--interactive: Prompt at each task.--next-issue: Jump to Step 2b (Issue-to-ship workflow).
Step 2b: Next Issue Workflow
- Check for incomplete plan (prompt to replace).
- Fetch with
gh issue list. - Prioritize: bug/critical > security > feat > oldest.
- Select issue, create
.devloop/plan.mdwith required frontmatter (title, issue, url, status). - Post-completion: Validate (tests/lint) and commit with
Closes #N.
Step 3: Resume State
If .devloop/next-action.json exists, load and resume.
Step 4: Setup Execution
Unless --interactive, create .claude/ralph-loop.local.md with iteration limits and completion promise: <promise>ALL PLAN TASKS COMPLETE</promise>.
Optional: Sync plan to native tasks with ${CLAUDE_PLUGIN_ROOT}/scripts/sync-plan-to-tasks.sh.
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 · 113 lines · 9 tokens per session scan A aa3bab737d3e
run is a skill published in the GitHub repository Zate/cc-plugins (10 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 1,221 once invoked, about $0.0000 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…