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.
npx skills add arozumenko/sdlc-skills --skill atlassian-contentgit clone --depth 1 https://github.com/arozumenko/sdlc-skillsWrote 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.
[](https://agentmods.dev/skills/arozumenko/sdlc-skills/atlassian-content)<a href="https://agentmods.dev/skills/arozumenko/sdlc-skills/atlassian-content"><img src="https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/atlassian-content/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.
<a href="https://agentmods.dev/skills/arozumenko/sdlc-skills/atlassian-content"><img src="https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/atlassian-content.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00067 | $0.04931 |
| Opus 5 | $0.00034 | $0.02465 |
| Sonnet 5 | $0.00013 | $0.00986 |
| Haiku 4.5 | $0.00007 | $0.00493 |
Grade A, and why
atlassian-content scanned grade A with 1 finding 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 11d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
## Transport — MCP preferred, curl fallback, browser last resort How it starts
The opening of the file, as written. The whole thing — 402 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atlassian content — Jira + Confluence, done right
Atlassian has two deployments (Cloud and Server / Data Center)
and two content surfaces (Jira and Confluence). That's a 2×2
grid of formats, mention syntaxes, and API versions — and markdown
is none of them. Content submitted in the wrong format renders as
a wall of asterisks, broken tables, orphan @username strings,
and code blocks that display as plain paragraphs. This skill is
the rulebook for getting it right the first time and verifying it
after.
Core principle: Detect the deployment, format-match the surface, resolve identities before you post, and always re-fetch what you wrote.
When to load this skill
Load when the task involves authoring content inside Atlassian products:
- Filing a Jira issue (story, bug, task, subtask)
- Leaving a Jira comment (review findings, clarifications, updates)
- Updating a Jira field that accepts rich text (description, custom text fields)
- Creating or editing a Confluence page (decisions, runbooks, writeups, reviews)
- Mentioning a human in either surface
Do NOT load for: read-only Jira/Confluence operations (search, field reads, user lookups) — those don't need formatting rules.
Absolute boundaries
-
Never post markdown into Jira or Confluence. Each deployment / surface has a specific expected format:
- Jira Cloud (API v3) → ADF (Atlassian Document Format, a structured JSON document).
- Jira Server / DC (API v2) → wiki markup (plain string,
e.g.
h2. Title,*bold*,{code}…{code}). - Confluence Cloud + Server / DC → storage format (an
XHTML-ish markup with
<ac:*>/<ri:*>macros — same on both deployments). Confluence Server also accepts wiki markup viabody.wikiinput as a one-shot convenience.
None of these surfaces interpret markdown natively via the API.
-
Never mention by
@usernamefree-text. Each deployment has its own mention syntax:- Cloud (both Jira and Confluence) → mention by
accountId(ADFmentionnode /<ri:user ri:account-id="…"/>). - Jira Server / DC →
[~username]inside wiki markup, whereusernameis the loginnamefrom/rest/api/2/user/search. - Confluence Server / DC →
<ri:user ri:userkey="…"/>or<ri:user ri:username="…"/>inside storage format.
- Cloud (both Jira and Confluence) → mention by
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 402 lines · 67 tokens per session scan A e684df49a482
atlassian-content is a skill published in the GitHub repository arozumenko/sdlc-skills (20 stars, last pushed today), licensed MIT. It adds 67 tokens to every session and 4,931 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
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.
remove
Remove a deployed framework or addon from the current workspace.