Atlassian Rovo MCP Server is a cloud-hosted bridge that lets compatible AI tools access Atlassian Cloud data and actions through the Model Context Protocol. Developers and project teams use it with Jira, Confluence, Jira Service Management, Bitbucket, Compass, Loom, and other Atlassian services, authenticated through OAuth 2.1 or API tokens. The catalogue entries provide skills, MCP connections, and a plugin for using the server.
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 atlassian/atlassian-mcp-server --skill triage-issuegit clone --depth 1 https://github.com/atlassian/atlassian-mcp-serverWrote 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/atlassian/atlassian-mcp-server/triage-issue)<a href="https://agentmods.dev/skills/atlassian/atlassian-mcp-server/triage-issue"><img src="https://agentmods.dev/badge/skills/atlassian/atlassian-mcp-server/triage-issue/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/atlassian/atlassian-mcp-server/triage-issue"><img src="https://agentmods.dev/badge/skills/atlassian/atlassian-mcp-server/triage-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 568 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00116 | $0.05193 |
| Opus 5 | $0.00058 | $0.02596 |
| Sonnet 5 | $0.00023 | $0.01039 |
| Haiku 4.5 | $0.00012 | $0.00519 |
Grade A, and why
triage-issue 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 5d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- triage-issue — 100% identical, 67 lines differ
- triage-issue — 97% identical, 133 lines differ
How it starts
The opening of the file, as written. The whole thing — 736 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage Issue
Keywords
triage bug, check duplicate, is this a duplicate, search for similar issues, create bug ticket, file a bug, report this error, triage this error, bug report, error message, similar issues, duplicate bug, who fixed this, has this been reported, search bugs, find similar bugs, create issue, file issue
Overview
Automatically triage bug reports and error messages by searching Jira for duplicates, identifying similar past issues, and helping create well-structured bug tickets or add context to existing issues. This skill eliminates manual duplicate checking and ensures bugs are properly documented with relevant historical context.
Use this skill when: Users need to triage error messages, bug reports, or issues to determine if they're duplicates and take appropriate action.
Workflow
Follow this 6-step process to effectively triage issues:
Step 1: Extract Key Information
Analyze the bug report or error message to identify search terms.
Extract These Elements:
Error signature:
- Error type or exception name (e.g., "NullPointerException", "TimeoutError")
- Error code or status (e.g., "500", "404", "ERR_CONNECTION_REFUSED")
- Specific error message text (key phrases, not full stack trace)
Context:
- Component or system affected (e.g., "authentication", "payment gateway", "API")
- Environment (e.g., "production", "staging", "mobile app")
- User actions leading to error (e.g., "during login", "when uploading file")
Symptoms:
- Observable behavior (e.g., "page blank", "infinite loading", "data not saving")
- Impact (e.g., "users can't login", "payments failing")
Example Extractions:
Input: "Users getting 'Connection timeout' error when trying to login on mobile app" Extracted:
- Error: "Connection timeout"
- Component: "login", "mobile app"
- Symptom: "can't login"
Input: "NullPointerException in PaymentProcessor.processRefund() line 245" Extracted:
- Error: "NullPointerException"
- Component: "PaymentProcessor", "refund"
- Location: "processRefund line 245"
What ships with it
2 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.
- 5d ago Changed · +35 lines 8b9f857efb4a
- 9d ago First seen · 701 lines · 116 tokens per session scan A 4ce1808138ea
triage-issue is a skill published in the GitHub repository atlassian/atlassian-mcp-server (1,023 stars, last pushed 5d ago), licensed Apache-2.0. It adds 116 tokens to every session and 5,193 once invoked, about $0.0006 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.
Other skills, from other repositories
node-inspect-debugger
Debug Node.js via --inspect + Chrome DevTools Protocol CLI.
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
sdlc-review
Review Kanban handoffs and route verified outcomes.
inspecting-hermes-desktop-dom
Read the live Hermes desktop DOM/CSS over CDP.
agent-merge-conflict-arbiter
Neutral arbiter for merge conflicts between two agents.
meeting-action-items
Turn meeting notes into cited decisions, owners, tickets.