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 skills add skyfox675/agents-skills --skill gh-issue-labelsgit clone --depth 1 https://github.com/skyfox675/agents-skillsWrote 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/skyfox675/agents-skills/gh-issue-labels)<a href="https://agentmods.dev/skills/skyfox675/agents-skills/gh-issue-labels"><img src="https://agentmods.dev/badge/skills/skyfox675/agents-skills/gh-issue-labels/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/skyfox675/agents-skills/gh-issue-labels"><img src="https://agentmods.dev/badge/skills/skyfox675/agents-skills/gh-issue-labels.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00179 | $0.04340 |
| Opus 5 | $0.00089 | $0.02170 |
| Sonnet 5 | $0.00036 | $0.00868 |
| Haiku 4.5 | $0.00018 | $0.00434 |
Grade A, and why
gh-issue-labels 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 7d 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 — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issue Labels
A small set of GitHub labels forms the persistent, auditable control plane between human operators and orchestrating agents. Labels survive across sessions, are visible to every concurrent operator, and are machine-readable in pre-dispatch filters — properties that chat instructions and issue comments do not have. This skill defines the full taxonomy: what each label means, who sets it, who consumes it, and the resolution rules when signals conflict.
Companion skills: issue selection and the dispatch brief live in the
dispatching-subagents skill; the claim/lock/release protocol behind agent-claimed
lives in the gh-issue-locking skill; the slot loop that reads these labels every round
lives in the orchestrating-slots skill; PR-side mechanics behind do-not-rebase live
in the driving-prs-to-merge skill. The Jira equivalent (Jira fields/labels instead of
GitHub labels) is the jira-issue-fields skill.
Project bindings
Adopting projects define these values in their own CLAUDE.md. Refer to them by placeholder everywhere below.
| Binding | Meaning | Example |
|---|---|---|
<workhorse-model> |
Default model for all code-writing dispatches | sonnet |
<cheap-model> |
Model for narrow mechanical tasks only — deliberately has NO label | haiku |
<premium-models> |
Operator-gated high-attention models (one label each) | opus, fable |
<integration-branch> |
Branch PRs target (affects close-on-merge, see gh-issue-locking) | dev |
<repo-slug> |
org/repo for --repo flags in label REST calls; see gh-issue-filing for the canonical definition |
acme/widgets |
<auto-rebase-automation> |
Whatever workflow/bot rebases open PRs onto <integration-branch> |
a scheduled auto-rebase workflow |
<operator-logins> |
GitHub logins of humans running orchestrators concurrently — resolved at runtime; assignees are set via gh api user --jq .login |
resolve dynamically |
<lock-comment-format> |
Parseable lock-comment marker paired with agent-claimed — full spec in gh-issue-locking |
<!-- claude-lock: ... --> |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 302 lines · 179 tokens per session scan A 7808e9512bc8
gh-issue-labels is a skill published in the GitHub repository skyfox675/agents-skills (10 stars, last pushed 10d ago), licensed MIT. It adds 179 tokens to every session and 4,340 once invoked, about $0.0009 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-09-03.
Other skills, from other repositories
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
github-notification-triage
Triage GitHub notifications and issue/PR queues.