A connection between an agent and Jira, a tool teams use to track software issues, projects, sprints, and work requests.

Use it to create, search, update, assign, link, and move Jira issues, as well as inspect sprints and epics.

It keeps engineering and operational work in one place and links tasks such as bugs or support actions to the people and projects responsible for them.

jira — Skill for Claude Code and Codex by iblai

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 iblai/enterprise-agents --skill jira

Clone the repo

git clone --depth 1 https://github.com/iblai/enterprise-agents

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/iblai/enterprise-agents/jira/github.svg)](https://agentmods.dev/skills/iblai/enterprise-agents/jira)

Your own site

<a href="https://agentmods.dev/skills/iblai/enterprise-agents/jira"><img src="https://agentmods.dev/badge/skills/iblai/enterprise-agents/jira/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/iblai/enterprise-agents/jira"><img src="https://agentmods.dev/badge/skills/iblai/enterprise-agents/jira.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 621 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found 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.

Model	Per session	Once invoked
Fable 5.1	$0.00037	$0.00621
Opus 5	$0.00018	$0.00311
Sonnet 5	$0.00007	$0.00124
Haiku 4.5	$0.00004	$0.00062

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

Security

Grade A, and why

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

skills/jira/SKILL.md · 39 lines

How it starts

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

Jira

What it is

Jira by Atlassian is the most widely used issue and project tracking platform in enterprise engineering, IT, and operations teams. In this segment, agents use Jira to link support tickets to engineering bugs, create action items from meeting notes, check sprint progress for engineering advisors, and track operational project milestones. It is also used as the backing store for Jira Service Management (IT help desk) requests.

When to use this skill

Creating a bug report or feature request linked to a customer support case
Adding action items extracted from a meeting as Jira issues with assignees and due dates
Checking sprint status, velocity, or remaining points for an engineering team
Querying open issues by component, label, or assignee for a standup summary
Transitioning an issue status (e.g., In Progress to Done) on behalf of a team member

Credentials

This skill authenticates using variables from ~/.openclaw/.env (template: .env.example at the config root). Required variables:

JIRA_BASE_URL - base URL of the Jira instance (e.g. https://mycompany.atlassian.net)
JIRA_USER_EMAIL - email address of the service account
JIRA_API_TOKEN - API token generated from the Atlassian account portal

Key operations

GET /rest/api/3/issue/{issueIdOrKey} - retrieve a specific issue
POST /rest/api/3/issue - create a new issue
PUT /rest/api/3/issue/{issueIdOrKey} - update issue fields
POST /rest/api/3/issue/{issueIdOrKey}/transitions - transition issue to a new status
GET /rest/api/3/search?jql=... - run a JQL query to find issues
GET /rest/api/3/board/{boardId}/sprint - list sprints for an agile board

Notes

Authentication uses HTTP Basic with email + API token (not password) for cloud instances.
Server/Data Center instances may use Personal Access Tokens instead of API tokens.
JQL (Jira Query Language) is the primary filter mechanism; test queries in the Jira UI first.
Rate limit is 10 requests/second per token for cloud; respect Retry-After headers on 429 responses.
Field IDs (e.g., customfield_10014 for story points) vary per instance; use /rest/api/3/field to discover them.

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

10d ago First seen · 39 lines · 37 tokens per session scan A 4086f333f079

Subscribe to this mod's changes

jira is a skill published in the GitHub repository iblai/enterprise-agents (11 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 621 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-08-30.

Project management agentic-ai ai-agents anthropic claude conversational-ai employee-experience

servicenow

ServiceNow (Healthcare IT) — lets an agent create, update, and query IT service management tickets, knowledge articles, and configuration items within a ServiceNow instance deployed in a health system.

iblai/medical-healthcare-agents · 42 tokens

parallel-feature-development

Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…

wshobson/agents · 105 tokens

saga-orchestration

Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…

wshobson/agents · 91 tokens

jira