Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Zate/cc-plugins/plugin install devloopWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/zate/cc-plugins/issues)<a href="https://agentmods.dev/skills/zate/cc-plugins/issues"><img src="https://agentmods.dev/badge/skills/zate/cc-plugins/issues/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/zate/cc-plugins/issues"><img src="https://agentmods.dev/badge/skills/zate/cc-plugins/issues.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00010 | $0.00838 |
| Opus 5.5 | $0.00004 | $0.00335 |
| Sonnet 5.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 1mo 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.
- 1mo 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 2mo ago), licensed MIT. It adds 10 tokens to every session and 838 once invoked, about $0.0000 per session on Opus 5.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
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
remove
Remove a deployed framework or addon from the current workspace.