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/issuesnpx skills add Zate/cc-plugins --skill issuesgit 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.00838 |
| Opus 5 | $0.00005 | $0.00419 |
| Sonnet 5 | $0.00002 | $0.00168 |
| Haiku 4.5 | $0.00001 | $0.00084 |
Grade A, and why
issues 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 `preferred_method` is "gh" or "curl":** How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issues - List GitHub Issues
Display GitHub issues for the current repository. You execute this directly.
Step 1: Check GitHub Setup
"${CLAUDE_PLUGIN_ROOT}/scripts/check-gh-setup.sh"
Parse the JSON output and check preferred_method:
If preferred_method is "none":
Check the specific issue:
- If
gh_installedis false:
GitHub CLI is not installed.
To install:
- macOS: brew install gh
- Windows: winget install GitHub.cli
- Linux: See https://github.com/cli/cli/blob/trunk/docs/install_linux.md
Alternatively, set a GITHUB_TOKEN environment variable to use the API directly.
- If
gh_installedis true butgh_authenticatedis false:
GitHub CLI is installed but not authenticated.
Run: gh auth login
This will guide you through authentication with your GitHub account.
Then exit - do not continue to Step 2.
If preferred_method is "gh" or "curl":
Continue to Step 2.
Step 2: Parse Arguments
Parse $ARGUMENTS for filter options:
--state STATE- Filter by state: open (default), closed, all--label LABEL- Filter by label (can appear multiple times)--assignee USER- Filter by assignee
Build the command arguments.
Step 3: Fetch and Display Issues
"${CLAUDE_PLUGIN_ROOT}/scripts/list-issues.sh" [options from step 2]
Display the formatted output to the user.
If no issues found:
No issues found matching your criteria.
Try different filters:
- /devloop:issues --state all
- /devloop:issues --state closed
Step 4: Offer Next Actions
AskUserQuestion:
questions:
- question: "What would you like to do?"
header: "Action"
multiSelect: false
options:
- label: "Start work on an issue"
description: "Use /devloop:plan --from-issue <number>"
- label: "Filter differently"
description: "Search with different criteria"
- label: "Done"
description: "Exit issue list"
If "Start work on an issue":
Ask which issue number, then run /devloop:plan --from-issue <number>
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 · 145 lines · 10 tokens per session scan A fd77d5b032ee
issues 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 838 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…