atlassian-admin

atlassian-admin is a skill for Claude Code, Codex from mrDesign-ww/vault-os. It costs 98 tokens per session (3,007 once invoked), scanned A, a copy of atlassian-admin, MIT.

An administration guide for Atlassian products, including Jira for issue tracking, Confluence for shared documentation, Bitbucket for code hosting, and Trello for task boards. It covers users, permissions, security, integrations, and organization-wide settings.

In plain words
What is it for?
Use it to add or remove users, assign product access, change permissions, configure administration settings, and manage ownership of Jira and Confluence content.
Why use it?
It provides procedures for managing access safely and consistently, including checking a departing user's work and transferring ownership.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to add or remove users, assign product access, change permissions, configure administration settings, and manage ownership of Jira and Confluence content.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mrdesign-ww/vault-os/atlassian-admin
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 mrDesign-ww/vault-os --skill atlassian-admin
Clone the repo
git clone --depth 1 https://github.com/mrDesign-ww/vault-os

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.

agentmods badge for atlassian-admin

README.md
[![agentmods](https://agentmods.dev/badge/skills/mrdesign-ww/vault-os/atlassian-admin.svg)](https://agentmods.dev/skills/mrdesign-ww/vault-os/atlassian-admin)
Your own site
<a href="https://agentmods.dev/skills/mrdesign-ww/vault-os/atlassian-admin"><img src="https://agentmods.dev/badge/skills/mrdesign-ww/vault-os/atlassian-admin.svg" alt="Measured on agentmods" height="20"></a>
Per session 98 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,007 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 100% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00098 $0.03007
Opus 5 $0.00049 $0.01503
Sonnet 5 $0.00020 $0.00601
Haiku 4.5 $0.00010 $0.00301

Measured 8d ago against content hash 44933862df55, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

atlassian-admin 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 8d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/permission_audit_tool.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Origin

This is a copy

100% identical to atlassian-admin — 2 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.

shell/claude/skills/atlassian-admin/SKILL.md · 231 lines

How it starts

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

Atlassian Administrator Expert

Workflows

User Provisioning

  1. Create user account: admin.atlassian.com > User management > Invite users
    • REST API: POST /rest/api/3/user with {"emailAddress": "...", "displayName": "...","products": [...]}
  2. Add to appropriate groups: admin.atlassian.com > User management > Groups > [group] > Add members
  3. Assign product access (Jira, Confluence) via admin.atlassian.com > Products > [product] > Access
  4. Configure default permissions per group scheme
  5. Send welcome email with onboarding info
  6. NOTIFY: Relevant team leads of new member
  7. VERIFY: Confirm user appears active at admin.atlassian.com/o/{orgId}/users and can log in

User Deprovisioning

  1. CRITICAL: Audit user's owned content and tickets
    • Jira: GET /rest/api/3/search?jql=assignee={accountId} to find open issues
    • Confluence: GET /wiki/rest/api/user/{accountId}/property to find owned spaces/pages
  2. Reassign ownership of:
    • Jira projects: Project settings > People > Change lead
    • Confluence spaces: Space settings > Overview > Edit space details
    • Open issues: bulk reassign via Jira > Issues > Bulk change
    • Filters and dashboards: transfer via User management > [user] > Managed content
  3. Remove from all groups: admin.atlassian.com > User management > [user] > Groups
  4. Revoke product access
  5. Deactivate account: admin.atlassian.com > User management > [user] > Deactivate
    • REST API: DELETE /rest/api/3/user?accountId={accountId}
  6. VERIFY: Confirm GET /rest/api/3/user?accountId={accountId} returns "active": false
  7. Document deprovisioning in audit log
  8. USE: Jira Expert to reassign any remaining issues

Group Management

  1. Create groups: admin.atlassian.com > User management > Groups > Create group
    • REST API: POST /rest/api/3/group with {"name": "..."}
    • Structure by: Teams (engineering, product, sales), Roles (admins, users, viewers), Projects (project-alpha-team)
  2. Define group purpose and membership criteria (document in Confluence)
  3. Assign default permissions per group
  4. Add users to appropriate groups
  5. VERIFY: Confirm group members via GET /rest/api/3/group/member?groupName={name}
  6. Regular review and cleanup (quarterly)
  7. USE: Confluence Expert to document group structure

Read the full file on GitHub · 231 lines

Files

What ships with it

4 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.

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.

  1. 8d ago First seen · 231 lines · 98 tokens per session scan A 44933862df55

Subscribe to this mod's changes

atlassian-admin is a skill published in the GitHub repository mrDesign-ww/vault-os (2 stars, last pushed today), licensed MIT. It adds 98 tokens to every session and 3,007 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to atlassian-admin, differing in 2 lines, and is treated as a copy.

Related

Other skills, from other repositories

neat-freak

Knowledge and governance closeout: reconcile project docs, rule files (CLAUDE.md/AGENTS.md), authorized agent memory, and workspace residue with what the code and runtime actually do, so the next session or the next person starts from one current answer. Trigger when the user names "neat-freak", "洁癖", or "/neat" — and…

KKKKhazix/khazix-skills · 202 tokens

issue-triage

Triage and categorize GitHub issues with priority labels. Use when user says "triage issues", "check issues", "review open issues", or during regular maintenance of GitHub issue backlog.

decebals/claude-code-java · 44 tokens

feature-dev

Guide a feature implementation through a structured seven-phase workflow with deep codebase understanding, clarifying questions, parallel architecture design, and quality review. Use this skill when the user asks to build a new feature, add functionality, or wants a methodical approach to implementation rather than…

waybarrios/opencode-power-pack · 62 tokens

product-manager-toolkit

Use when the user needs product management workflows such as RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, go-to-market strategy, feature prioritization, research synthesis, or requirements documentation.

majiayu000/spellbook · 47 tokens

ijfw-workflow

Use when the user says: 'build', 'create', 'plan', 'new project', 'brainstorm', 'design', 'UI', 'website', 'dashboard', 'app', 'help me build', 'launch', 'book', 'campaign', or anything project-level. Skill body decides Quick vs Deep path.

FerroxLabs/ijfw · 70 tokens

ijfw-plan

Use when the user says 'plan this', 'plan it', 'make a plan', 'let's plan', 'draft a plan', 'how should we tackle this', 'break this down', or invokes '/ijfw-plan'. Produces a falsifiable PLAN.md (software, book, campaign, design, research) with task breakdown, dependency wave-table, and success criteria — gated by…

FerroxLabs/ijfw · 95 tokens