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 eric861129/SKILLS_All-in-one --skill atlassiangit clone --depth 1 https://github.com/eric861129/SKILLS_All-in-oneWrote 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/eric861129/skills_all-in-one/atlassian)<a href="https://agentmods.dev/skills/eric861129/skills_all-in-one/atlassian"><img src="https://agentmods.dev/badge/skills/eric861129/skills_all-in-one/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/eric861129/skills_all-in-one/atlassian"><img src="https://agentmods.dev/badge/skills/eric861129/skills_all-in-one/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.00096 | $0.01528 |
| Opus 5.5 | $0.00038 | $0.00611 |
| Sonnet 5.5 | $0.00019 | $0.00306 |
| Haiku 4.5 | $0.00010 | $0.00153 |
Grade A, and why
atlassian 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 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.
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.
This is a copy
100% identical to atlassian — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atlassian (Jira + Confluence)
Full Jira and Confluence integration with two authentication methods:
- OAuth 2.1 via Atlassian MCP server — browser-based consent, auto-refresh tokens, calls MCP tools
- API token — email + token stored in keyring, calls REST API directly
First-Time Setup
Option 1: OAuth 2.1 via MCP Server (Recommended)
No API tokens or instance URLs needed. Uses dynamic client registration and PKCE.
pip install -r requirements.txt
python scripts/auth.py login --oauth
A browser opens for Atlassian authorization. Select which products (Jira, Confluence, Compass) to grant access. Tokens are stored in the system keyring and auto-refresh when expired.
Check status:
python scripts/auth.py status
Option 2: API Token (Fallback)
For environments where browser-based OAuth isn't available.
pip install -r requirements.txt
python scripts/auth.py login
Follow the prompts to enter your Atlassian URL, email, and API token. Credentials are stored securely in the system keyring.
Create an API token at: https://id.atlassian.com/manage-profile/security/api-tokens
Check authentication status:
python scripts/auth.py status
Logout (clears both OAuth and API token credentials):
python scripts/auth.py logout
Backend Selection
The scripts automatically detect which backend to use based on your auth type:
- OAuth → MCP backend (calls Atlassian MCP server tools)
- API token → REST backend (calls Atlassian REST API directly)
All commands work identically regardless of backend.
Jira (scripts/jira.py)
Search issues with JQL
python scripts/jira.py search "project = DEV AND status = Open"
python scripts/jira.py search "assignee = currentUser() ORDER BY updated DESC" --limit 10
Get issue details
python scripts/jira.py get DEV-123
Create an issue
python scripts/jira.py create --project DEV --summary "Fix login bug" --type Bug
python scripts/jira.py create --project DEV --summary "New feature" --type Story \
--description "Details here" --priority High --assignee "[email protected]" --labels "backend,urgent"
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.
- 1mo ago First seen · 224 lines · 96 tokens per session scan A 473cefc1d2f2
atlassian is a skill published in the GitHub repository eric861129/SKILLS_All-in-one (52 stars, last pushed 6mo ago), licensed MIT. It adds 96 tokens to every session and 1,528 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to atlassian, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
portfolio-manager
Plan this week's budget split between projects from the portfolio snapshot and priorities.md, then report it to the operator.
portfolio-fixture
The zero-judgement test of the portfolio flow. Copies a fixed plan to the outbox and reports it.
himalayas-employer
AI hiring assistant for Himalayas. Post remote jobs, manage company profiles, source talent, message candidates, and benchmark salaries using the Himalayas MCP server.
learn
Record a correction, decision, finding or failed attempt in the wiki. Use when the user corrects you, when a decision is made with a reason, when an experiment returns a verdict, or when you learn something the next session would otherwise re-derive.
loop
Work through the taskboard unattended for hours, pacing against the usage limits and filling the gap before a reset with CPU-only jobs. Use when asked to run all day, work unattended, or loop over tickets.
wrap-up
Close out a task by folding what it taught into the wiki, updating the taskboard, and linting. Use at the end of a task, before clearing a session, or when asked to wrap up.