A setup guide for connecting an MCP server to Jira and finding the project's default Jira settings.

Installing or reconfiguring Jira integration so other tools can create tickets with the correct server and project defaults.

It checks what is already configured and asks only for missing details such as the Jira address, authentication, project, or board.

jira-setup — Skill by kolodkin

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.

agentmods

npx agentmods add skills/kolodkin/devpowers/jira-setup

Any agent

npx skills add kolodkin/devpowers --skill jira-setup

Clone the repo

git clone --depth 1 https://github.com/kolodkin/devpowers

Made for: Claude Code, Codex.

Per session 142 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,751 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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	$0.00142	$0.01751
Opus 5	$0.00071	$0.00875
Sonnet 5	$0.00028	$0.00350
Haiku 4.5	$0.00014	$0.00175

Measured 2d ago against content hash af0f41d85c1b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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-setup/SKILL.md · 123 lines

How it starts

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

Jira Setup

Walk through the steps below and prompt only for what's missing. Re-running this is safe — values that are already set are reported and skipped.

Step 0 — Ensure the mcp-atlassian MCP server is registered

This skill (and jira-ticket) drive Jira through the mcp__mcp-atlassian__* tools. Check whether mcp__mcp-atlassian__jira_create_issue is visible in your tool list.

If it's visible, the server is registered. Skip to Step 1.
If it's missing, hand off to the setup-mcp skill, which is the bounded installer for this plugin's MCP servers — mcp-atlassian is already in its manifest. Invoke setup-mcp via the Skill tool with mcp-atlassian (e.g. /setup-mcp mcp-atlassian). It shows the proposed config, asks for scope, registers the server, and verifies the uvx prerequisite. Because MCP servers only load at startup, it will tell the user to restart Claude Code — so once it returns, tell the user to restart and re-run /jira-setup (or /jira-ticket), then stop. The tools won't be available until the restart.

If the setup-mcp skill isn't available in this session for any reason, fall back to instructing the user: "Run /setup-mcp mcp-atlassian, restart Claude Code, then re-run /jira-setup."

Step 1 — Validate credentials

Run this exact command:

echo "JIRA_URL=${JIRA_URL:-NOT_SET}" && \
echo "JIRA_USERNAME=${JIRA_USERNAME:-NOT_SET}" && \
echo "JIRA_API_TOKEN=${JIRA_API_TOKEN:+SET}" && \
echo "JIRA_PERSONAL_TOKEN=${JIRA_PERSONAL_TOKEN:+SET}"

JIRA_URL is always required. For auth, either the Cloud combo (JIRA_USERNAME + JIRA_API_TOKEN) or the Server / Data Center PAT (JIRA_PERSONAL_TOKEN) must be set. If neither is complete, instruct the user and stop. Do not proceed.

JIRA_URL is NOT_SET → "Set your Jira workspace URL, e.g. export JIRA_URL=https://yourworkspace.atlassian.net"
Cloud (Atlassian-hosted, *.atlassian.net): set both
- JIRA_USERNAME → your account email, e.g. export [email protected]
- JIRA_API_TOKEN → create one at https://id.atlassian.com/manage-profile/security/api-tokens, then export JIRA_API_TOKEN=<your-token>
Server / Data Center (self-hosted): set just
- JIRA_PERSONAL_TOKEN → create a Personal Access Token in your Jira profile, then export JIRA_PERSONAL_TOKEN=<your-pat>. JIRA_USERNAME is optional here, but if you set it the jira-ticket skill will use it for the assignee / reporter on created tickets.

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

2d ago First seen · 123 lines · 142 tokens per session scan A af0f41d85c1b

Subscribe to this mod's changes

jira-setup is a skill published in the GitHub repository kolodkin/devpowers (2 stars, last pushed 23d ago), licensed MIT. It adds 142 tokens to every session and 1,751 once invoked, about $0.0007 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-31.

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens