A GitHub issue triage workflow that reads an issue, matches it to existing labels, and suggests new labels when the current set is insufficient. Labels are tags used to organize issues.

It helps classify a specified GitHub issue and apply relevant labels. It can also recommend labels that the repository does not yet have.

It makes issue categorization more consistent and avoids manually checking every available label.

label-issue — Skill for Claude Code by tomzx/agents

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 tomzx/agents --skill label-issue

Clone the repo

git clone --depth 1 https://github.com/tomzx/agents

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/tomzx/agents/label-issue/github.svg)](https://agentmods.dev/skills/tomzx/agents/label-issue)

Your own site

<a href="https://agentmods.dev/skills/tomzx/agents/label-issue"><img src="https://agentmods.dev/badge/skills/tomzx/agents/label-issue/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/tomzx/agents/label-issue"><img src="https://agentmods.dev/badge/skills/tomzx/agents/label-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 544 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.

Model	Per session	Once invoked
Fable 5.1	$0.00024	$0.00544
Opus 5.5	$0.00010	$0.00218
Sonnet 5.5	$0.00005	$0.00109
Haiku 4.5	$0.00002	$0.00054

Measured 22d ago against content hash e15c3cba4dee, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

label-issue 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 22d 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.

skills/label-issue/SKILL.md · 97 lines

How it starts

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

Label GitHub Issue

Reads a GitHub issue and applies appropriate existing labels based on its content, then recommends new labels if the current set is insufficient.

Prerequisites

gh CLI authenticated with triage or write access to the repository
Issue number ($1) referencing an existing issue in the current repository context

Workflow

Fetch issue details ($1)
        |
        v
Fetch available labels
        |
        v
Match issue content to labels
        |
        v
Matching labels found?
   /         \
 Yes           No
  |             |
  v             v
Apply labels  Skip label
via gh        add step
  |             |
  +------+------+
         |
         v
New labels needed?
   /         \
 Yes           No
  |             |
  v             v
Recommend     Done
new labels

Steps

Fetch the issue details:
```
ghx issue view $1
```
Fetch all available labels:
```
gh label list
```

Match the issue content to existing labels and apply them:

gh issue edit $1 --add-label "<label1>" --add-label "<label2>"

If no existing labels adequately categorize the issue, recommend new labels with suggested names and descriptions.

Example Usage

Scenario 1: Bug report

/label-issue 42

Issue describes a crash in the login flow. Applies: bug, authentication. No new labels needed.

Scenario 2: Feature request with no matching label

/label-issue 100

Issue requests a dark mode toggle. No ui or enhancement label exists. Applies feature-request if available, recommends creating a ui label.

Scenario 3: Duplicate issue

/label-issue 55

Issue is a known duplicate. Applies duplicate label. Recommends closing with a reference to the original.

Useful Commands Reference

Command	Description
`ghx issue view <issue-number>`	Fetch issue title, body, and current labels (cached)
`gh label list`	List all available labels in the repository
`gh issue edit <issue-number> --add-label "<label>"`	Apply one or more labels to an issue

Read the full file on GitHub · 97 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.

22d ago Changed · +6 lines e15c3cba4dee
1mo ago First seen · 91 lines · 24 tokens per session scan A 51a387e8dcd5

Subscribe to this mod's changes

label-issue is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 544 once invoked, about $0.0001 per session on Opus 5.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.

Project management

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

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…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

qa-project-bootstrap

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…

petrkindlmann/qa-skills · 124 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens