jira-setup

jira-setup is a skill for Claude Code, Codex from bmbouter/redhat-agents. It costs 23 tokens per session (628 once invoked), scanned A, original, Apache-2.0.

A setup guide for connecting Jira, Atlassian’s issue and project-tracking service, through MCP tools. It explains how to create an Atlassian API token and add the connection settings.

In plain words
What is it for?
Use it before using Jira-connected agents, when Jira tools are not already configured on the machine.
Why use it?
It avoids configuration mistakes and keeps the token out of project files while preparing the Jira connection.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Claude Code.

Good fit Use it before using Jira-connected agents, when Jira tools are not already configured on the machine.

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

agentmods badge for jira-setup

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/bmbouter/redhat-agents/jira-setup"><img src="https://agentmods.dev/badge/skills/bmbouter/redhat-agents/jira-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 628 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00023 $0.00628
Opus 5.5 $0.00009 $0.00251
Sonnet 5.5 $0.00005 $0.00126
Haiku 4.5 $0.00002 $0.00063

Measured 1mo ago against content hash 0fb533991dfd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

jira-setup 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 1mo 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.

module/skills/jira-setup/SKILL.md · 85 lines

How it starts

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

When to Use

Run this before using any Jira-connected agents. Required once per machine.

Instructions

Walk the user through the following steps. Pause after each step and confirm before proceeding.

Step 1: Check for existing Atlassian MCP configuration

Check whether the user's AI tool already has Atlassian MCP tools configured. Look for an existing mcp__plugin_atlassian_atlassian__ tool prefix or similar Atlassian/Jira integration.

If already configured, skip to Step 4 (verification).

Step 2: Create an Atlassian API token

Tell the user:

To connect to Jira, you need an Atlassian API token. Follow these steps:

  1. Go to https://id.atlassian.com/manage-profile/security/api-tokens
  2. Click Create API token
  3. Give it a name like "AI Agent Access"
  4. Copy the token — you will not be able to see it again

Paste the token here when ready.

Wait for the user to provide the token. Do NOT store the token in any file — it should only go into the MCP configuration.

Step 3: Configure MCP settings

The Atlassian MCP plugin needs the following configuration. Guide the user to add this to their AI tool's MCP settings (e.g., Claude Code's settings.json, .claude.json, or equivalent):

{
  "mcpServers": {
    "atlassian": {
      "type": "plugin",
      "id": "atlassian",
      "config": {
        "atlassianEmail": "<user's email>",
        "atlassianApiToken": "<token from step 2>",
        "atlassianUrl": "https://<instance>.atlassian.net"
      }
    }
  }
}

Ask the user for:

  • Their Atlassian email address
  • Their Jira instance URL (e.g., https://yourcompany.atlassian.net)
  • The API token from Step 2

Help them place the configuration in the correct file for their tool.

Step 4: Verify connectivity

Test the connection by searching for a known project:

searchJiraIssuesUsingJql:
  jql: "project = <project_key> ORDER BY updated DESC"
  maxResults: 1

If this succeeds, tell the user Jira is connected and ready.

Read the full file on GitHub · 85 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. 1mo ago First seen · 85 lines · 23 tokens per session scan A 0fb533991dfd

Subscribe to this mod's changes

jira-setup is a skill published in the GitHub repository bmbouter/redhat-agents (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 628 once invoked, about $0.0001 per session on Opus 5.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-31.