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 Unique-Divine/jiyuu --skill gh-labelsgit clone --depth 1 https://github.com/Unique-Divine/jiyuuWrote 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/unique-divine/jiyuu/gh-labels)<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.
<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>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.00096 | $0.01277 |
| Opus 5 | $0.00048 | $0.00639 |
| Sonnet 5 | $0.00019 | $0.00255 |
| Haiku 4.5 | $0.00010 | $0.00128 |
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.
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/25uty9w5S-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 specificedS-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 urgentprio-p1-high: (#aaeaec) | Priority: Highprio-p2-normal: (#aaeaec) | Priority: Normalprio-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.
- Pick the repo — default: current git checkout. Otherwise
-R OWNER/REPO. - See what exists —
gh label list(add-Rif needed). - Create only what is missing — one
gh label createper label from My Labels, using the exact description and color from the bullet. - If the label already exists but is wrong — rerun the same command with
--forceto update color and description without deleting the label.
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.
- 9d ago First seen · 130 lines · 96 tokens per session scan A 39350722d18c
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.
Other skills, from other repositories
commit-generate
Generate bilingual (English + Traditional Chinese) commit message from git changes.
version-generate
A release-note generator that reads changes from the latest Git tag to the current code and recommends a new semantic version. It writes versioned notes and updates a main changelog index.
vhs-e2e-gif
Record a test run, a TUI session, or any terminal command as a GIF with VHS and attach it to a GitHub PR as a release-hosted asset, never a repo commit. Use when asked to record an e2e run, demo a fix on a PR, attach a GIF or screen recording to a pull request, show a test passing visually, or produce a terminal…
check-linters-before-commit
Before any commit, run linters, vet, tests, and build verification; do not commit until checks pass.
merge-conflict-resolution
Active merge conflicts. Use when an in-progress merge, rebase, cherry-pick, or revert has conflicted hunks that require intent reconstruction, resolution, proof, and continuation.
gh-skill
Manage agent skills with gh skill. Use this skill to discover, preview, install, update, and publish Agent Skills so an agent can self-manage the skills available in its environment.