Borrowing it
Nothing to install: this file belongs to reboulip/rblclass. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/reboulip/rblclass/main/.claude/skills/gh-issues/SKILL.mdgit clone --depth 1 https://github.com/reboulip/rblclassWrote 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/reboulip/rblclass/gh-issues)<a href="https://agentmods.dev/skills/reboulip/rblclass/gh-issues"><img src="https://agentmods.dev/badge/skills/reboulip/rblclass/gh-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/reboulip/rblclass/gh-issues"><img src="https://agentmods.dev/badge/skills/reboulip/rblclass/gh-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.00034 | $0.02285 |
| Opus 5.5 | $0.00014 | $0.00914 |
| Sonnet 5.5 | $0.00007 | $0.00457 |
| Haiku 4.5 | $0.00003 | $0.00229 |
Grade A, and why
gh-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 2mo 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.
`curl -L -o <scratchpad-path> <url>` (or `gh api`), not `WebFetch` — WebFetch How it starts
The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/gh-issues — plan open GH issues into the roadmap
What this does
- Fetches all open GH issues not yet carrying a disposition label (
roadmap,deferred, ordropped). - Reads each one and classifies its nature.
- Triages each issue with the user — implement, drop, or defer — and immediately applies the decided disposition (label + comment) before planning starts.
- For issues marked implement: proposes a roadmap mapping, asks disambiguation questions as needed, writes items to
ROADMAP.md, labels each issueroadmap, and posts a roadmap-link comment.
Step 1 — Fetch open issues
gh issue list --state open --json number,title,labels,body --limit 100
Filter out any issue that already carries one of the following labels — those are already triaged:
roadmapdeferreddropped
Also scan ROADMAP.md for [#N] back-references. If an issue number appears there but lacks the roadmap label, it is effectively planned — add the label silently and skip it from the triage flow.
Re-review already-labelled open issues. Labelled issues (roadmap,
deferred) that are still open are not necessarily settled: view each one
(gh issue view <n> --json ...,comments,updatedAt) and check for comments
added after the disposition was applied — new repro data, a fix that did
not hold, a follow-up suggestion. Any issue with substantive news re-enters
the flow: summarise what changed and ask the user (per issue, via
AskUserQuestion) whether to (re-)plan it, keep its current disposition, or
adjust labels. A roadmap-labelled issue whose planned fix shipped but
demonstrably failed gets a new roadmap item; a deferred issue with a
concrete new proposal may be promoted.
If no unresolved issues remain after filtering and re-review, report that and stop.
Step 2 — Read issue details
For each unresolved issue:
gh issue view <number> --json number,title,body,labels,comments
Classify each issue as one of:
- Bug — defect in existing functionality.
- Enhancement — improvement to existing functionality.
- Feature — new capability.
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.
- 2mo ago First seen · 236 lines · 34 tokens per session scan A f19fd06ec875
gh-issues is a skill published in the GitHub repository reboulip/rblclass (12 stars, last pushed yesterday), licensed Apache-2.0. It adds 34 tokens to every session and 2,285 once invoked, about $0.0001 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-30.
gh-issues compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| gh-issuesreboulip/rblclass | Skill | 12 | yesterday | Apache-2.0 | A | 34 | Claude Code |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |