jira-integration

jira-integration is a skill for Claude Code, Codex from gongyijie85/dsh-ecc. It costs 37 tokens per session (2,333 once invoked), scanned A, a copy of jira-integration, MIT.

A Jira integration for an AI coding workflow. Jira is a tool for tracking work items such as bugs, tasks, and feature requests.

In plain words
What is it for?
It helps retrieve and search tickets, turn requirements into testable criteria, add comments, change statuses, and link branches or merge requests to issues.
Why use it?
It keeps ticket details and progress updates in the coding workflow, so you do not have to switch tools or copy status information by hand.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths.

Good fit It helps retrieve and search tickets, turn requirements into testable criteria, add comments, change statuses, and link branches or merge requests to issues.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gongyijie85/dsh-ecc/jira-integration
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 gongyijie85/dsh-ecc --skill jira-integration
Clone the repo
git clone --depth 1 https://github.com/gongyijie85/dsh-ecc

Made for: Claude Code, Codex.

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.

agentmods badge for jira-integration

README.md
[![agentmods](https://agentmods.dev/badge/skills/gongyijie85/dsh-ecc/jira-integration/github.svg)](https://agentmods.dev/skills/gongyijie85/dsh-ecc/jira-integration)
Your own site
<a href="https://agentmods.dev/skills/gongyijie85/dsh-ecc/jira-integration"><img src="https://agentmods.dev/badge/skills/gongyijie85/dsh-ecc/jira-integration/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.

agentmods 80×15 button for jira-integration

Your own site · 80×15
<a href="https://agentmods.dev/skills/gongyijie85/dsh-ecc/jira-integration"><img src="https://agentmods.dev/badge/skills/gongyijie85/dsh-ecc/jira-integration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,333 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 94% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00037 $0.02333
Opus 5 $0.00018 $0.01167
Sonnet 5 $0.00007 $0.00467
Haiku 4.5 $0.00004 $0.00233

Measured 7d ago against content hash 4cabafb56cf0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

jira-integration 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 7d 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.

If MCP is not available, use the Jira REST API v3 directly via `curl` or a helper script.
Origin

This is a copy

94% identical to jira-integration — 28 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/jira-integration/SKILL.md · 304 lines

How it starts

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

Jira Integration Skill

Retrieve, analyze, and update Jira tickets directly from your AI coding workflow. Supports both MCP-based (recommended) and direct REST API approaches.

When to Activate

  • Fetching a Jira ticket to understand requirements
  • Extracting testable acceptance criteria from a ticket
  • Adding progress comments to a Jira issue
  • Transitioning a ticket status (To Do → In Progress → Done)
  • Linking merge requests or branches to a Jira issue
  • Searching for issues by JQL query

Prerequisites

Option A: MCP Server (Recommended)

Install the mcp-atlassian MCP server. This exposes Jira tools directly to your AI agent.

Requirements:

  • Python 3.10+
  • uvx (from uv), installed via your package manager or the official uv installation documentation

Add to your MCP config (e.g., ~/.claude.jsonmcpServers):

{
  "jira": {
    "command": "uvx",
    "args": ["mcp-atlassian==0.21.0"],
    "env": {
      "JIRA_URL": "https://YOUR_ORG.atlassian.net",
      "JIRA_EMAIL": "[email protected]",
      "JIRA_API_TOKEN": "your-api-token"
    },
    "description": "Jira issue tracking — search, create, update, comment, transition"
  }
}

Security: Never hardcode secrets. Prefer setting JIRA_URL, JIRA_EMAIL, and JIRA_API_TOKEN in your system environment (or a secrets manager). Only use the MCP env block for local, uncommitted config files.

To get a Jira API token:

  1. Go to https://id.atlassian.com/manage-profile/security/api-tokens
  2. Click Create API token
  3. Copy the token — store it in your environment, never in source code

Option B: Direct REST API

If MCP is not available, use the Jira REST API v3 directly via curl or a helper script.

Required environment variables:

Variable Description
JIRA_URL Your Jira instance URL (e.g., https://yourorg.atlassian.net)
JIRA_EMAIL Your Atlassian account email
JIRA_API_TOKEN API token from id.atlassian.com

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

  1. 7d ago First seen · 304 lines · 37 tokens per session scan A 4cabafb56cf0

Subscribe to this mod's changes

jira-integration is a skill published in the GitHub repository gongyijie85/dsh-ecc (7 stars, last pushed 3d ago), licensed MIT. It adds 37 tokens to every session and 2,333 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 94% identical to jira-integration, differing in 28 lines, and is treated as a copy.

Related

Other skills, from other repositories