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 darellchua2/opencode-config-template --skill jira-ticket-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/jira-ticket-labeler-skill)<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/jira-ticket-labeler-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/jira-ticket-labeler-skill/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/darellchua2/opencode-config-template/jira-ticket-labeler-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/jira-ticket-labeler-skill.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.00036 | $0.02498 |
| Opus 5 | $0.00018 | $0.01249 |
| Sonnet 5 | $0.00007 | $0.00500 |
| Haiku 4.5 | $0.00004 | $0.00250 |
Grade A, and why
jira-ticket-labeler-skill scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Fallback: classification/label-mapping is analytical and can proceed without MCP; only ticket creation/reads (`atlassian_createJiraIssue`, `atlassian_getJiraIssue`) need the server or the REST fallback (`curl -u email: How it starts
The opening of the file, as written. The whole thing — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
I provide intelligent JIRA ticket classification by:
- Analyzing ticket content to determine appropriate issue type (Bug, Story, Task, Epic)
- Assigning priority levels using JIRA's priority field (Highest, High, Medium, Low, Lowest)
- Adding JIRA components for area classification
- Using Atlassian MCP tools for all JIRA operations
- Supporting cross-platform workflows (GitHub issue → JIRA ticket mapping)
When to use me
Use this when:
- You need to classify JIRA tickets with correct issue types
- You want to set appropriate priorities on JIRA tickets
- You're creating JIRA tickets from GitHub issue context
- You need consistent ticket classification across your JIRA project
- You want to map GitHub labels to JIRA issue types
Prerequisites
atlassianMCP server enabled in this session — it is disabled by default (opt-in). Ifatlassian_*tools are absent from your tool list, do NOT attempt or hallucinate them:- Interactive: offer per-project enable via
opencode-repo-setup-skill(effective next session). - Fallback: classification/label-mapping is analytical and can proceed without MCP; only ticket creation/reads (
atlassian_createJiraIssue,atlassian_getJiraIssue) need the server or the REST fallback (curl -u email:token). - Otherwise: return the classification and report creation as skipped.
- Interactive: offer per-project enable via
- JIRA project access with create/edit permissions
- Valid JIRA project key (e.g., "IBIS", "PROJ")
Why a Separate Skill from git-issue-labeler
JIRA and GitHub use fundamentally different taxonomy systems:
| Aspect | GitHub | JIRA |
|---|---|---|
| Classification | Labels (flat, multiple) | Issue Type (single, structured) |
| Priority | Labels (priority: high) |
Dedicated Priority field (dropdown) |
| Area | Labels | Components (separate entity) |
| Subtasks | Not supported natively | First-class citizen |
| Epics | Label-based | Dedicated Epic issue type |
GitHub git-issue-labeler-skill handles GitHub labels. This skill handles JIRA taxonomy.
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.
- 5d ago First seen · 311 lines · 36 tokens per session scan A bf858da87884
jira-ticket-labeler-skill is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed 3d ago), licensed Apache-2.0. It adds 36 tokens to every session and 2,498 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
Jira QA Workflows
Run QA work in Jira like a professional, bug lifecycle and triage, JQL queries for testers, quality dashboards, sprint QA rituals, and REST API automation for bulk bug operations and reporting.
jira-time-tracking
Time tracking, worklogs, and time reports. TRIGGERS: 'log time', 'time spent on', 'log hours', 'log work', 'worklog', 'time tracking', 'timesheet', 'how much time', 'time logged', 'time report', 'export timesheet', 'set estimate', 'remaining estimate', 'original estimate'. Use for time-related queries and operations…
jira-administration
Complete JIRA project and system administration including projects, automation rules, permissions, users, notifications, screens, issue types, and workflows. Use when managing project structure, automating work, configuring team access, or setting up issue tracking.
jira-custom-fields
Custom field discovery and configuration. TRIGGERS: 'field ID for', 'what's the field ID', 'what is the field ID', 'list custom fields', 'what fields are available', 'what custom fields', 'show custom fields', 'customfield', 'find field', 'agile fields', 'configure agile fields', 'story points field'. Use for JIRA…
jira-issue-management
Core JIRA issue CRUD - create bugs/tasks/stories, get issue details, update fields, delete issues. TRIGGERS: 'show me [KEY]', 'get issue [KEY]', 'view issue', 'create a bug/task/story', 'update [KEY]', 'delete [KEY]', 'details of [KEY]', 'look up [KEY]', 'what's in [KEY]'. NOT FOR: epics (use jira-agile)…
jira-service-management
Complete ITSM/ITIL workflow support for JSM - service desks, requests, SLAs, customers, approvals, knowledge base. Use when managing service desk requests, tracking SLAs, or handling customer operations.