gh-labels

gh-labels is a skill for Claude Code, Codex from Unique-Divine/jiyuu. It costs 96 tokens per session (1,277 once invoked), scanned A, original, MIT.

A reference for GitHub issue and pull-request labels used in this workspace. GitHub is a service for hosting code, while labels are tags that describe work status, priority, or area.

In plain words
What is it for?
Use it to understand labels such as triage, needs scope, implementation-ready, blocked, priority levels, and development-tool areas, or to add those labels with the GitHub command-line tool.
Why use it?
It removes guesswork when choosing labels and keeps project tracking consistent. It also explains how to create missing labels in a repository.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to understand labels such as triage, needs scope, implementation-ready, blocked, priority levels, and development-tool areas, or to add those labels with the GitHub command-line tool.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/unique-divine/jiyuu/gh-labels
Install

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.

Any agent
npx skills add Unique-Divine/jiyuu --skill gh-labels
Clone the repo
git clone --depth 1 https://github.com/Unique-Divine/jiyuu

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for gh-labels

README.md
[![agentmods](https://agentmods.dev/badge/skills/unique-divine/jiyuu/gh-labels/github.svg)](https://agentmods.dev/skills/unique-divine/jiyuu/gh-labels)
Your own site
<a href="https://agentmods.dev/skills/unique-divine/jiyuu/gh-labels"><img src="https://agentmods.dev/badge/skills/unique-divine/jiyuu/gh-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.

agentmods 80×15 button for gh-labels

Your own site · 80×15
<a href="https://agentmods.dev/skills/unique-divine/jiyuu/gh-labels"><img src="https://agentmods.dev/badge/skills/unique-divine/jiyuu/gh-labels.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 96 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,277 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00096 $0.01277
Opus 5 $0.00048 $0.00639
Sonnet 5 $0.00019 $0.00255
Haiku 4.5 $0.00010 $0.00128

Measured 9d ago against content hash 39350722d18c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

gh-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 9d 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.

ai-skills/gh-labels/SKILL.md · 130 lines

How it starts

The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GitHub labels

Reference for what labels mean, then how to add them to a repo that does not have them yet.

My Labels

Prefix convention:

  • S-* labels describe issue status.
  • prio-p* labels describe issue priority.
  • A-* labels describe product or engineering areas.
Status (S) Labels
  • S-triage: (#F9D0C4) | Status: This issue is waiting on initial triage. More Info: https://tinyurl.com/25uty9w5
  • S-needs-scope: (#f08583) | Needs someone to work further on the design for the feature or fix. NOT YET accepted.
  • S-impl: (#04d0e4) | Status: Implementation-ready. Clear and fully specificed
  • S-blocked: (#f08583) | Status: 🧱 Blocked by an external dependency or unresolved decision.
  • S-someday-maybe: (#f08583) | Status: 🤔 Intentionally paused. Currently on hold or out of scope.
Priority Labels
  • prio-p0-critical: (#aaeaec) | Priority: Critical or super urgent
  • prio-p1-high: (#aaeaec) | Priority: High
  • prio-p2-normal: (#aaeaec) | Priority: Normal
  • prio-p3-low: (#aaeaec) | Priority: Low. Please focus on p2 or higher for now.
Area (A) Labels
  • A-dev-tools: (#eab6cb) | Area: Tools and changes for external developers and builders. NOT end users
    • Use for issues that improve SDKs, CLIs, examples, docs, codegen, APIs, or other tooling for external devs. NOT repo contributors.
    • Do not use for purely internal CI or repo automation.
    • You should rarely be using this label because we don't work on external dev tooling often. Most tool development is internal for employees and team members in the org.

When the user adds a standard label, append a bullet here with the same format: `<name>`: (#<RRGGBB>) | <description> - Keep their description text verbatim.

Add labels to a repo

Use this when a repo is missing labels from My Labels, or has stale name/color/description.

  1. Pick the repo — default: current git checkout. Otherwise -R OWNER/REPO.
  2. See what existsgh label list (add -R if needed).
  3. Create only what is missing — one gh label create per label from My Labels, using the exact description and color from the bullet.
  4. If the label already exists but is wrong — rerun the same command with --force to update color and description without deleting the label.

Read the full file on GitHub · 130 lines

Changes

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.

  1. 9d ago First seen · 130 lines · 96 tokens per session scan A 39350722d18c

Subscribe to this mod's changes

gh-labels is a skill published in the GitHub repository Unique-Divine/jiyuu (6 stars, last pushed 2d ago), licensed MIT. It adds 96 tokens to every session and 1,277 once invoked, about $0.0005 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-08-31.