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 agentmods add skills/darellchua2/opencode-config-template/git-issue-labeler-skillnpx skills add darellchua2/opencode-config-template --skill git-issue-labeler-skillgit clone --depth 1 https://github.com/darellchua2/opencode-config-templateWrote 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/darellchua2/opencode-config-template/git-issue-labeler-skill)<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/git-issue-labeler-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/git-issue-labeler-skill.svg" alt="Measured on agentmods" 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.00037 | $0.03207 |
| Opus 5 | $0.00018 | $0.01604 |
| Sonnet 5 | $0.00007 | $0.00641 |
| Haiku 4.5 | $0.00004 | $0.00321 |
Grade A, and why
git-issue-labeler-skill 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 2d 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 — 361 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
I provide intelligent GitHub issue label assessment by:
- Analyzing issue content to determine appropriate labels
- Using keyword and pattern matching to identify issue types and priorities
- Assigning single or multiple labels based on issue complexity
- Auto-creating missing labels before assignment (never fails on missing labels)
- Providing label descriptions for clarity and consistency
When to use me
Use this when:
- You need to assess and label GitHub issues automatically
- You want consistent label assignment across your repository
- You need to categorize issues using GitHub's default label scheme
- You're setting up a new repository and need label guidelines
- You want to review unlabeled or mislabeled issues
- You need to assign semantic versioning labels to pull requests
Prerequisites
- GitHub CLI (
gh) installed and authenticated - Git repository with GitHub remote
- Write access to the GitHub repository
- Valid
GITHUB_TOKENorghauthentication setup
Governance
The semantic versioning label definitions below follow semantic-release-convention, which is the single source of truth for version bump conventions across all skills and agents.
For JIRA ticket type and priority mapping, see jira-ticket-labeler-skill — a separate skill for JIRA-specific taxonomy.
Label Taxonomy
Issue Labels vs PR Labels
| Context | Label Set | Purpose |
|---|---|---|
| GitHub Issues | Type labels + Priority labels | Categorize and triage issues |
| GitHub PRs | Semver labels (major, minor, patch) | Determine version bump for release |
Issues get type + priority labels. PRs get exactly one semver label. These are distinct concerns.
Label Categories
1. Type Labels (GitHub Issues)
| Label | Color | Hex | Description |
|---|---|---|---|
bug |
Red | #d73a4a | Something isn't working as expected |
enhancement |
Light blue | #a2eeef | New feature or improvement |
documentation |
Blue | #0075ca | Documentation improvements |
duplicate |
Gray | #cfd3d7 | Already exists |
good first issue |
Green | #7057ff | Good for newcomers |
help wanted |
Purple | #008672 | Extra attention needed |
invalid |
Yellow | #e4e669 | Not a valid issue |
question |
Purple | #d876e3 | Clarification needed |
wontfix |
White | #ffffff | Will not be worked on |
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.
- 2d ago First seen · 361 lines · 37 tokens per session scan A ce330471c34a
git-issue-labeler-skill is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed 5d ago), licensed Apache-2.0. It adds 37 tokens to every session and 3,207 once invoked, about $0.0002 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
git-ship
自动化 Git 工作流一键发布助手，执行完整的「ship」流程： 基于最新 main 切新分支 → commit → 推送 → 创建 PR → squash merge → 回 main。 调用 ship 本身就是对完整流程的授权；自动推断分支名、commit message 和 PR 内容， 并主动解决 Git 冲突、测试、lint、类型检查、构建和 CI 失败，持续修复和重试， 直到改动成功合并。不要因可自行修复的失败暂停，只在认证、权限、仓库保护等 无法由当前环境解决的外部阻塞出现时请求用户介入。 仅在用户明确表达「ship」意图时触发，例如： 直接说「ship」「/ship」「git ship」 明确要求完整走完 git…
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.