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/newnpx skills add Zate/cc-plugins --skill newgit 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.00015 | $0.01448 |
| Opus 5 | $0.00008 | $0.00724 |
| Sonnet 5 | $0.00003 | $0.00290 |
| Haiku 4.5 | $0.00002 | $0.00145 |
Grade A, and why
new scanned grade A 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**If "gh" or "curl":** Continue to GitHub Mode (unless `--local` specified). How it starts
The opening of the file, as written. The whole thing — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
New Issue - Create GitHub Issue
Create a GitHub issue via gh issue create. You do the work directly.
Use --local for offline/private work in .devloop/issues/.
Step 1: Parse Arguments and Check GitHub
Check $ARGUMENTS for title/description and --local flag.
"${CLAUDE_PLUGIN_ROOT}/scripts/check-gh-setup.sh"
If preferred_method is "none":
gh_installed: false: Display install instructions, fall back to--localgh_authenticated: false: Promptgh auth login, fall back to--local
If "gh" or "curl": Continue to GitHub Mode (unless --local specified).
Step 2: GitHub Mode
2.1 Collect Info
AskUserQuestion:
questions:
- question: "What type of issue?"
header: "Type"
multiSelect: false
options:
- label: "Bug"
description: "Something isn't working correctly"
- label: "Feature"
description: "New functionality or enhancement"
- label: "Task"
description: "General work item or chore"
- question: "Add labels?"
header: "Labels"
multiSelect: true
options:
- label: "bug"
description: "Bug fix"
- label: "enhancement"
description: "New feature or improvement"
- label: "devloop"
description: "Related to devloop plugin"
- label: "documentation"
description: "Documentation update"
Auto-add type label: Bug → "bug", Feature → "enhancement".
2.2 Title and Body
If no title in arguments, prompt for it. Then ask for description (what, why, context, acceptance criteria).
2.3 Create Issue
gh issue create \
--title "${title}" \
--body "${body}" \
--label "${labels_comma_separated}" \
--repo $(git remote get-url origin | sed 's/.*[:/]\([^/]*\/[^/]*\)\.git/\1/')
Parse issue URL and number from output.
2.4 Next Actions
AskUserQuestion:
questions:
- question: "Issue #N created. What next?"
header: "Next"
multiSelect: false
options:
- label: "Start work"
description: "Create plan from this issue"
- label: "Create more"
description: "Create another issue"
- label: "View issues"
description: "List all open issues"
- label: "Done"
description: "Return to conversation"
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 · 235 lines · 15 tokens per session scan A 0491684a4aed
new is a skill published in the GitHub repository Zate/cc-plugins (10 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 1,448 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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…