A command-line tool for working with Atlassian Jira, Confluence, and Bitbucket Server or Data Center. It includes rules for searching, reading, comparing, editing, and safely publishing Atlassian content.

Use it for Jira issue searches, Confluence page reading and text updates, and Bitbucket work on self-hosted Atlassian systems.

It reduces mistakes caused by the tools' exact command syntax and version handling. It also helps avoid publishing changes when the remote content has changed or approval is required.

atls — Skill for Claude Code and Codex by eunsanMountain

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 eunsanMountain/atlassian-skills --skill atls

Clone the repo

git clone --depth 1 https://github.com/eunsanMountain/atlassian-skills

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/eunsanmountain/atlassian-skills/atls/github.svg)](https://agentmods.dev/skills/eunsanmountain/atlassian-skills/atls)

Your own site

<a href="https://agentmods.dev/skills/eunsanmountain/atlassian-skills/atls"><img src="https://agentmods.dev/badge/skills/eunsanmountain/atlassian-skills/atls/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/eunsanmountain/atlassian-skills/atls"><img src="https://agentmods.dev/badge/skills/eunsanmountain/atlassian-skills/atls.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 3,290 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.00137	$0.03290
Opus 5	$0.00068	$0.01645
Sonnet 5	$0.00027	$0.00658
Haiku 4.5	$0.00014	$0.00329

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

Security

Grade A, and why

atls 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 12d 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.

src/atlassian_skills/_assets/skills/atls/SKILL.md · 158 lines

How it starts

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

atls — Atlassian CLI dispatcher

Load this skill before any atls command. Use --help for uncommon operations and atls version --check when a command is missing.

Syntax agents often get wrong

JQL/CQL is positional: atls jira issue search "project=PROJ".
Spell output --format=json; -f means --md-file on md push.
compact for scans, JSON for decisions, md for reading, raw for byte-exact.
compare is a local file against the live remote; diff is two things already on the server.
Main groups: jira, confluence, bitbucket. There is no runtime state group.

Invariants

Run only next_actions[].argv, exactly as returned; never compose one. requires_user_approval=true is never auto-run. Zero PUT before approval or on an unresolved conflict; storage publishes only the approved hash.

Choose the Confluence workflow

Read/summarize: page get ID --body-repr=md. On content_complete=false the Markdown is missing text — re-read with the returned --body-repr=view argv before summarizing. Reads change nothing; do it without asking.
One exact text leaf: dry-run page patch-text ID --find OLD --replace NEW --if-version N; repeat only when one occurrence is patchable.
Structure/table/macro/image edit: page inspect ID --intent=structure-edit --format=json first; in_place_blocked means only append or patch-text lands. Then md pull.
Existing managed file: validate/compare/proof-push without an unnecessary get or repull.
Locally authored Markdown: page create or page update --body-format md. Local ![](x.png) uploads from the body file's directory; --asset-dir moves that base, stdin requires it. Every publish re-uploads pictures — prefer md push for a page edited twice. On created_with_missing_images run the returned page recover-assets argv; rerunning the write recovers nothing.
Storage the user supplied: page update --body-format storage.

Managed md push and stateless page update --body-format md emit different raw JSON/status; branch on outcome, not field equality. md compare is a three-way Markdown comparison, not a storage-candidate proof.

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

12d ago First seen · 158 lines · 137 tokens per session scan A 609a3d186336

Subscribe to this mod's changes

atls is a skill published in the GitHub repository eunsanMountain/atlassian-skills (21 stars, last pushed 1mo ago), licensed MIT. It adds 137 tokens to every session and 3,290 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-30.

Claude Code Project management atlassian cli codex confluence jira

c-jira

Manage Jira issues using jira (jira-cli). List and filter issues, create new tickets, transition issue status, manage sprints, and add comments — all from the terminal without opening a browser.

daxaur/openpaw · 45 tokens

pm-skills

Use when coordinating project-delivery work across the 8 project-management sub-skills — sprint/velocity analytics, portfolio health, Jira/JQL, Confluence, Atlassian admin, templates, meeting analysis, team comms. Triggers on 'our sprints feel off', 'project health report', 'audit our Jira permissions', 'when will it…

mrDesign-ww/vault-os · 179 tokens

Jira QA Workflows

Run QA work in Jira like a professional, bug lifecycle and triage, JQL queries for testers, quality dashboards, sprint QA rituals, and REST API automation for bulk bug operations and reporting.

PramodDutta/qaskills · 45 tokens

jira-administration

Complete JIRA project and system administration including projects, automation rules, permissions, users, notifications, screens, issue types, and workflows. Use when managing project structure, automating work, configuring team access, or setting up issue tracking.

grandcamel/JIRA-Assistant-Skills · 51 tokens

jira-service-management

Complete ITSM/ITIL workflow support for JSM - service desks, requests, SLAs, customers, approvals, knowledge base. Use when managing service desk requests, tracking SLAs, or handling customer operations.

grandcamel/JIRA-Assistant-Skills · 47 tokens

jira-time-tracking

Time tracking, worklogs, and time reports. TRIGGERS: 'log time', 'time spent on', 'log hours', 'log work', 'worklog', 'time tracking', 'timesheet', 'how much time', 'time logged', 'time report', 'export timesheet', 'set estimate', 'remaining estimate', 'original estimate'. Use for time-related queries and operations…

grandcamel/JIRA-Assistant-Skills · 121 tokens