A procedure for updating Jira cards, which are work-tracking records, through Atlassian's official connection. It first reads the card, identifies the changes, and adds structured comments.

Use it to record progress, changes, or status updates on a Jira card. You must provide the card's link, and the official Atlassian connection must be available.

It reduces the risk of updating the wrong card or using an unsupported connection.

jira-update — Skill for Claude Code and Codex by whitebeardit

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 whitebeardit/.cursor --skill skill-jira-update

Clone the repo

git clone --depth 1 https://github.com/whitebeardit/.cursor

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/whitebeardit/.cursor/skill-jira-update/github.svg)](https://agentmods.dev/skills/whitebeardit/.cursor/skill-jira-update)

Your own site

<a href="https://agentmods.dev/skills/whitebeardit/.cursor/skill-jira-update"><img src="https://agentmods.dev/badge/skills/whitebeardit/.cursor/skill-jira-update/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/whitebeardit/.cursor/skill-jira-update"><img src="https://agentmods.dev/badge/skills/whitebeardit/.cursor/skill-jira-update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,066 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.00042	$0.02066
Opus 5	$0.00021	$0.01033
Sonnet 5	$0.00008	$0.00413
Haiku 4.5	$0.00004	$0.00207

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

Security

Grade A, and why

jira-update 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 9d 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/shared/skill-jira-update/SKILL.md · 288 lines

How it starts

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

Jira Card Update Skill

This skill provides a safe, structured approach to updating Jira cards by reading card information, identifying changes, and adding professional comments using the official Atlassian MCP.

Critical Prerequisites

MCP Availability Check (MANDATORY)

BEFORE any action, you MUST verify if the official Atlassian MCP is available.

If the MCP is NOT available:

Display ONLY this message:

MCP oficial da Atlassian não foi localizado. Nenhuma ação foi executada.

Do NOT attempt to comment, update, or simulate any action on Jira
Do NOT proceed with any Jira-related operations

If the MCP is available:

Proceed with the workflow below
Use ONLY official Atlassian MCP tools
Never use unofficial integrations or alternatives

Workflow

Step 1: Request Jira Card Link (MANDATORY)

You MUST explicitly ask the user for the Jira card link.

❌ DO NOT:

Assume or infer which card to update
Use cards from conversation history without explicit confirmation
Proceed without the link

✅ DO:

Ask clearly: "Por favor, forneça o link do card do Jira que deve ser atualizado."
Wait for the user to provide the link
Only continue after receiving the link

Example:

Por favor, forneça o link do card do Jira que deve ser atualizado.

Step 2: Extract Card Information

From the provided Jira URL, extract:

Cloud ID: From URL format https://yoursite.atlassian.net/...
Issue Key: From URL or issue ID (e.g., PROJ-123)

URL Patterns:

https://yoursite.atlassian.net/browse/PROJ-123
https://yoursite.atlassian.net/jira/software/projects/PROJ/boards/1/backlog?selectedIssue=PROJ-123
Issue key format: PROJECT-KEY-NUMBER (e.g., PROJ-123)

Step 3: Read and Analyze Card

Use official Atlassian MCP tools to read the card:

Get Cloud ID (if needed):
- Use getAccessibleAtlassianResources to get available cloud IDs
- Or extract from URL: https://yoursite.atlassian.net → cloud ID

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

9d ago First seen · 288 lines · 42 tokens per session scan A 33aa0202abe1

Subscribe to this mod's changes

jira-update is a skill published in the GitHub repository whitebeardit/.cursor (12 stars, last pushed 6mo ago), licensed MIT. It adds 42 tokens to every session and 2,066 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

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens