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 aiocean/claude-plugins --skill aio-atlassiangit clone --depth 1 https://github.com/aiocean/claude-pluginsWrote 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/aiocean/claude-plugins/aio-atlassian)<a href="https://agentmods.dev/skills/aiocean/claude-plugins/aio-atlassian"><img src="https://agentmods.dev/badge/skills/aiocean/claude-plugins/aio-atlassian/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/aiocean/claude-plugins/aio-atlassian"><img src="https://agentmods.dev/badge/skills/aiocean/claude-plugins/aio-atlassian.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00077 | $0.02804 |
| Opus 5.5 | $0.00031 | $0.01122 |
| Sonnet 5.5 | $0.00015 | $0.00561 |
| Haiku 4.5 | $0.00008 | $0.00280 |
Grade A, and why
aio-atlassian 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 1mo 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.
- Deleting a comment → `curl -X DELETE .../rest/api/3/issue/PROJ-123/comment/{commentId}` How it starts
The opening of the file, as written. The whole thing — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atlassian CLI
Jira and Confluence operations via CLI tools from nguyenvanduocit/jira-mcp and nguyenvanduocit/confluence-mcp.
Environment
- Go: !
which go 2>/dev/null || echo "NOT INSTALLED" - jira-cli: !
which jira-cli 2>/dev/null || echo "NOT INSTALLED" - confluence-cli: !
which confluence-cli 2>/dev/null || echo "NOT INSTALLED" - ATLASSIAN_HOST: !
echo ${ATLASSIAN_HOST:-NOT SET} - ATLASSIAN_EMAIL: !
echo ${ATLASSIAN_EMAIL:-NOT SET} - ATLASSIAN_TOKEN: !
[ -n "$ATLASSIAN_TOKEN" ] && echo "SET" || echo "NOT SET"
Install
go install github.com/nguyenvanduocit/jira-mcp/cmd/jira-cli@latest
go install github.com/nguyenvanduocit/confluence-mcp/cmd/confluence-cli@latest
Or via Homebrew (confluence-cli only):
brew install nguyenvanduocit/tap/confluence-mcp
Credentials (get token from https://id.atlassian.com/manage-profile/security/api-tokens):
Create a .env file:
ATLASSIAN_HOST=https://your-company.atlassian.net
[email protected]
ATLASSIAN_TOKEN=your-api-token
All CLI commands accept --env .env to load credentials from this file.
Global flags: --env <path> (load .env file), --output text|json (output format, default: text)
Jira CLI
Issues
# Get issue (full details with transitions, changelog, subtasks, description)
jira-cli get-issue --issue-key PROJ-123 --env .env
jira-cli get-issue --issue-key PROJ-123 --fields summary,status --output json
jira-cli get-issue --issue-key PROJ-123 --expand transitions,changelog
# Search issues with JQL
jira-cli search-issues --jql "project = PROJ AND status = 'In Progress'" --env .env
jira-cli search-issues --jql "assignee = currentUser() AND sprint in openSprints()" --max-results 10 --env .env
jira-cli search-issues --jql "project = PROJ AND created >= -7d" --fields summary,status --env .env
# Create issue
jira-cli create-issue --project PROJ --summary "Bug title" --type Bug --env .env
jira-cli create-issue --project PROJ --summary "New feature" --type Story \
--description "## Overview\nA new feature" --priority High --env .env
jira-cli create-issue --project PROJ --summary "Task" --type Task \
--assignee 5a1234b --priority Medium --env .env
# Create child issue (subtask)
jira-cli create-child-issue --parent-key PROJ-100 --summary "Subtask 1" --env .env
jira-cli create-child-issue --parent-key PROJ-100 --summary "Subtask" \
--description "Details here" --type Subtask --env .env
# Update issue
jira-cli update-issue --issue-key PROJ-123 --summary "Updated title" --env .env
jira-cli update-issue --issue-key PROJ-123 --priority High --assignee 5a1234b --env .env
jira-cli update-issue --issue-key PROJ-123 --description "## New description" --env .env
# Delete issue (cannot be undone)
jira-cli delete-issue --issue-key PROJ-123 --env .env
# List available issue types
jira-cli list-issue-types --env .env
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.
- 1mo ago First seen · 255 lines · 77 tokens per session scan A 654d9334bf7e
aio-atlassian is a skill published in the GitHub repository aiocean/claude-plugins (4 stars, last pushed 1mo ago), licensed MIT. It adds 77 tokens to every session and 2,804 once invoked, about $0.0003 per session on Opus 5.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-09-03.
Other skills, from other repositories
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
plan-pipeline
Orchestrates the complete planning pipeline: product direction (ceo-review) -> architecture (eng-review) -> implementation plan (start) -> validation (validate) -> execution (execute). Run stages individually or let the orchestrator coordinate the full flow.
routines-discover
Analyzes the current project to surface high-value Routines use cases across the three trigger types (schedule, API, GitHub events). Usage: /routines-discover.
incremental-shipping
Use when implementing a non-trivial feature, migration, or refactor that would otherwise be a single large change. Activate for keywords like "feature flag", "incremental", "vertical slice", "migration", "rollout", "behind a flag", "ship small". Enforces vertical slicing, feature-flagged rollout, and refactor-with…
linear-app-setup
Create and configure a Linear agent app so the assistant can manage issues, projects, and workflows under its own identity.
product-brief
Extract a product idea through guided questions and generate a PRD. Use when the user says 'write a PRD', 'spec this feature', 'turn this idea into a brief'. Not for a non-product initiative like hiring or partnerships (use initiative-kickoff once shipped); not for checking existing projects' status (use…