agentmods.dev

atlassian-integration

atlassian-integration is a skill for Claude Code from ahmadulhoq/agentskel. It costs 41 tokens per session (1,083 once invoked), scanned A, original, MIT.

Guidance for safely reading and updating Jira issues and Confluence pages through connected tools. Jira tracks work tickets, while Confluence stores team documentation.

In plain words
What is it for?
Use it to inspect tickets, change their status, create follow-up work, and publish or update technical documents.
Why use it?
It reduces mistakes caused by different Jira workflows, such as choosing the wrong status transition or updating the wrong page.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: installed under .agents/ (shared by several agents).

Part of the agentskel plugin — 53 skills, 3 hooks shipped together

not rated 13repo 23d ago A scan 41 tokens original MIT

Good fit Use it to inspect tickets, change their status, create follow-up work, and publish or update technical documents.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ahmadulhoq/agentskel/atlassian-integration
View source ↗ ahmadulhoq/agentskel
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 ahmadulhoq/agentskel --skill atlassian-integration
Clone the repo
git clone --depth 1 https://github.com/ahmadulhoq/agentskel

Made for: Claude Code.

Or install agentskel, the plugin that ships this one along with the rest of its 53 skills, 3 hooks.

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 atlassian-integration

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/ahmadulhoq/agentskel/atlassian-integration"><img src="https://agentmods.dev/badge/skills/ahmadulhoq/agentskel/atlassian-integration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,083 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.00041 $0.01083
Opus 5 $0.00020 $0.00541
Sonnet 5 $0.00008 $0.00217
Haiku 4.5 $0.00004 $0.00108

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

Security

Grade A, and why

atlassian-integration 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 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.

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.

.agents/skills/atlassian-integration/SKILL.md · 79 lines

How it starts

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

Atlassian Integration

Purpose: Use Atlassian MCP tools correctly. Four known failure modes — this skill blocks all four.

When to use

Any workflow that reads or writes Jira or Confluence via MCP. This includes:

  • Reading a ticket to understand requirements
  • Transitioning ticket status
  • Creating new tickets (tech debt, follow-ups)
  • Publishing ADRs, postmortems, specs to Confluence
  • Commenting on tickets with PR links or status

Prerequisites

  • Atlassian MCP connected in your AI tool. Two options:
    • Rovo Cloud (official, OAuth) — tool names start with getJiraIssue, createJiraIssue, etc.
    • sooperset self-hosted (for Data Center / DC) — tool names start with jira_get_issue, jira_create_issue, etc.
  • This skill references actions abstractly ("the get-issue tool"). Agent uses whichever is available.
  • See docs/ATLASSIAN-SETUP.md for per-tool MCP setup.

Step 1 — Before transitioning a ticket

  • Call the list-transitions tool for the specific ticket (getTransitionsForJiraIssue on Rovo, equivalent on sooperset).
  • Match the desired event to the actual transition name in the response. Team workflows differ — "In Progress" on one project is "Started" on another.
  • Only then call the transition tool with the valid transition ID.

Why: hardcoded status names fail on custom workflows. Transitions are workflow-specific, not global.

Step 2 — Before creating a ticket

  • Call the issue type metadata tool (getJiraIssueTypeMetaWithFields on Rovo) for the project + issue type.
  • Note which fields are required (often includes custom fields: epic link, components, fix version, etc.).
  • Populate all required fields per .memory/JIRA_WORKFLOW.md conventions.
  • Then call the create-issue tool.

Why: required custom fields vary per project. Skipping this step gives cryptic "customfield_12345 is required" errors.

Step 3 — When reading Confluence content

  • Expect body format to vary: Rovo returns Markdown; sooperset may return wiki markup or ADF.
  • If the content looks structured (tables, code blocks), validate the format before piping into agent context.
  • For large pages (>50KB), consider using search tools (searchConfluenceUsingCql, search) to find the specific section rather than loading the whole page.

Read the full file on GitHub · 79 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 · 79 lines · 41 tokens per session scan A d8406de59d35

Subscribe to this mod's changes

atlassian-integration is a skill published in the GitHub repository ahmadulhoq/agentskel (13 stars, last pushed 23d ago), licensed MIT. It adds 41 tokens to every session and 1,083 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-09-02.

Project management
Related

Other skills, from other repositories

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