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-status-updater-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-status-updater-skill)<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/jira-status-updater-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/jira-status-updater-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-status-updater-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/jira-status-updater-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.00024 | $0.04856 |
| Opus 5 | $0.00012 | $0.02428 |
| Sonnet 5 | $0.00005 | $0.00971 |
| Haiku 4.5 | $0.00002 | $0.00486 |
Grade A, and why
jira-status-updater-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 6d 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: REST transition — `curl -u email:token -X POST https://<site>.atlassian.net/rest/api/3/issue/<KEY>/transitions` (cloudId: `curl https://<site>.atlassian.net/_edge/tenant_info`). How it starts
The opening of the file, as written. The whole thing — 598 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
I provide automated JIRA ticket status transitions to ensure proper workflow completion after PR merges:
- Detect JIRA Ticket: Extract JIRA ticket key from PR title, commits, or branch name
- Query Available Transitions: Use Atlassian API to get valid status transitions for the ticket
- Identify Target Status: Find "Done" or "Closed" status transition
- Execute Status Transition: Update JIRA ticket status using transition API
- Add Merge Comment: Post final comment with PR merge details
- Handle Edge Cases: Gracefully handle missing transitions, permissions, already-done status
- Log Status: Provide clear feedback on transition success/failure
When to use me
Use this framework when:
- A PR has been successfully merged
- You need to update the linked JIRA ticket status
- You want to ensure JIRA tickets are properly closed after work completion
- You're building a workflow that includes PR merge handling
- You need automated JIRA workflow management
This is a framework skill - it provides JIRA status transition functionality that other skills use.
MCP Availability Guard
Transitions/comments use atlassian_* MCP tools, and the atlassian MCP server is disabled by default (opt-in). Ticket-key detection (Step 1, git/gh based) always works; before the first atlassian_* call:
- If
atlassian_*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: REST transition —
curl -u email:token -X POST https://<site>.atlassian.net/rest/api/3/issue/<KEY>/transitions(cloudId:curl https://<site>.atlassian.net/_edge/tenant_info). - No credentials/headless: report the transition as skipped and log the detected ticket key — never fail the PR-merge workflow.
Core Workflow Steps
Step 1: Detect JIRA Ticket Reference
Purpose: Extract JIRA ticket key from PR or commit information
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.
- 6d ago First seen · 598 lines · 24 tokens per session scan A 25fb20c26153
jira-status-updater-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 24 tokens to every session and 4,856 once invoked, about $0.0001 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-developer-integration
Git and developer workflow integration. TRIGGERS: 'generate branch name', 'create branch name', 'branch name for', 'write PR description', 'PR description for', 'link PR', 'link pull request', 'parse commit', 'extract issue from commit', 'smart commit', 'development panel'. Use for Git, GitHub, GitLab, Bitbucket…
work-story
Work a user story end to end — fetch the ticket, plan (with approval), implement, verify the applicable gates, self-review, open the PR, and update the tracker. Use when given an issue key like PROJ-1234, ENG-42, or.
daf-workflow
DevAIFlow session context loader — reads session metadata, issue tracker tickets, and context files. Auto-activates when DAFSESSIONNAME is set. Also useful when asked about current task, session status, or workflow steps for daf open, daf new, daf git new, daf jira new, and daf investigate.
workingon
Record the work done in this Claude Code session in the configured ticketing tool (Jira, Linear, GitHub Issues, Trello or Vikunja), creating the ticket, adding a short progress comment, linking an existing one or closing it. Use it when the [workingon] hook reports unrecorded work, when the user types /workingon, and…
mk:jira-dev
Generate developer artifacts from Jira tickets via the jira-as wrapper: branch names, PR descriptions, parsed commits, commit/PR-to-issue links. Triggers: 'branch name for KEY', 'PR description for KEY', 'parse commits for issue keys', 'link PR to KEY'. NOT for executing git/gh commands directly (mk:ship); NOT for…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.