Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/darellchua2/opencode-config-templatenpx agentmods add skills/darellchua2/opencode-config-template/jira-git-integration-skillWrote 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-git-integration-skill)<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/jira-git-integration-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/jira-git-integration-skill.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 185 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 285 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.04164 |
| Opus 5 | $0.00012 | $0.02082 |
| Sonnet 5 | $0.00005 | $0.00833 |
| Haiku 4.5 | $0.00002 | $0.00416 |
Grade A, and why
jira-git-integration-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 4d 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 with an API token — `curl -u email:token` against `https://<site>.atlassian.net` (cloudId: `curl https://<site>.atlassian.net/_edge/tenant_info`); scoped tokens use `api.atlassian.com/ex/jira/{cloudId}`. How it starts
The opening of the file, as written. The whole thing — 608 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
I provide JIRA + Git integration utilities that can be used across multiple workflows:
- Get JIRA Resources: Detect and retrieve Atlassian cloud ID, visible projects, and accessible resources
- Get JIRA User Info: Retrieve current user's account ID for ticket assignment
- Create JIRA Tickets: Create new tasks, stories, or bugs in specified JIRA projects
- Add JIRA Comments: Add comments to existing JIRA tickets with Markdown formatting
- Upload Images to JIRA: Upload local images as JIRA attachments and retrieve attachment URLs
- Generate JIRA Branch Names: Create consistent branch names from JIRA tickets
- Fetch JIRA Issue Details: Retrieve ticket information including status, assignee, description
When to use me
Use this framework when:
- You need JIRA integration in a workflow
- You're creating a skill that requires JIRA ticket management
- You need to upload images to JIRA tickets
- You want to ensure consistent branch naming across JIRA workflows
- You need to add comments or attachments to JIRA tickets
This is a framework skill - it provides JIRA utilities that other skills use.
MCP Availability Guard
Every step below uses atlassian_* MCP tools, and the atlassian MCP server is disabled by default (opt-in). Before Step 1:
- 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 with an API token —
curl -u email:tokenagainsthttps://<site>.atlassian.net(cloudId:curl https://<site>.atlassian.net/_edge/tenant_info); scoped tokens useapi.atlassian.com/ex/jira/{cloudId}. - No credentials/headless: report the JIRA operation as skipped — never block the calling workflow.
Core Workflow Steps
Step 1: Get Accessible Atlassian Resources
Purpose: Retrieve cloud ID and list of accessible Atlassian resources
Tools Used: atlassian_getAccessibleAtlassianResources
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.
- 4d ago First seen · 608 lines · 24 tokens per session scan A 331472590be7
jira-git-integration-skill is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 24 tokens to every session and 4,164 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.