atlassian-admin

atlassian-admin is a skill for Codex from bestagentkits/agency-skills. It costs 98 tokens per session (3,006 once invoked), scanned A, original, MIT.

An administration guide for Atlassian products such as Jira, Confluence, Bitbucket, and Trello, covering users, access, security, integrations, and organization-wide settings.

In plain words
What is it for?
Use it to add or remove users, assign groups and product access, change permissions, reassign Jira and Confluence content, and configure administrative settings.
Why use it?
It helps administrators manage who can use which products and safely handle access changes, ownership transfers, and governance tasks.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it to add or remove users, assign groups and product access, change permissions, reassign Jira and Confluence content, and configure administrative settings.

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

Made for: 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/bestagentkits/agency-skills/atlassian-admin/github.svg)](https://agentmods.dev/skills/bestagentkits/agency-skills/atlassian-admin)
Your own site
<a href="https://agentmods.dev/skills/bestagentkits/agency-skills/atlassian-admin"><img src="https://agentmods.dev/badge/skills/bestagentkits/agency-skills/atlassian-admin/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.

agentmods 80×15 button for atlassian-admin

Your own site · 80×15
<a href="https://agentmods.dev/skills/bestagentkits/agency-skills/atlassian-admin"><img src="https://agentmods.dev/badge/skills/bestagentkits/agency-skills/atlassian-admin.svg" alt="Reviewed on agentmods" width="80" 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,006 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 original No closer match found 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.03006
Opus 5 $0.00049 $0.01503
Sonnet 5 $0.00020 $0.00601
Haiku 4.5 $0.00010 $0.00301

Measured 11d ago against content hash bd2cf8270a24, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, 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 11d 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

Copies of this mod

1 near-identical copy found in the catalogue:

skills/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

5 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. 11d ago First seen · 231 lines · 98 tokens per session scan A bd2cf8270a24

Subscribe to this mod's changes

atlassian-admin is a skill published in the GitHub repository bestagentkits/agency-skills (11 stars, last pushed 2mo ago), licensed MIT. It adds 98 tokens to every session and 3,006 once invoked, about $0.0005 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-31.

Related

Other skills, from other repositories

curate-collection

Build and maintain a library collection through acquisitions, weeding (deaccessioning), collection assessment, reader advisory, and interlibrary loan coordination. Covers selection criteria, collection development policies, the CREW/MUSTIE method for weeding, usage analysis, and responsive collection management. Use…

pjt222/agent-almanac · 105 tokens

design-on-call-rotation

Design sustainable on-call rotations with balanced schedules, clear escalation policies, fatigue management, and handoff procedures. Minimize burnout while maintaining incident response coverage. Use when setting up on-call for the first time, scaling a team from 2-3 to 5+ engineers, addressing on-call burnout or…

pjt222/agent-almanac · 86 tokens

design-training-program

Design a GxP training programme covering training needs analysis by role, curriculum design (regulatory awareness, system-specific, data integrity), competency assessment criteria, training record retention, and retraining triggers for SOP revisions and incidents. Use when a new validated system requires user training…

pjt222/agent-almanac · 91 tokens

conduct-retrospective

Conduct a project or sprint retrospective by gathering data from status reports and velocity metrics, structuring what went well and what needs improvement, and generating actionable improvement items with owners and due dates. Use at the end of a sprint, after a project phase or milestone, following a significant…

pjt222/agent-almanac · 83 tokens

create-github-issues

Structured GitHub issue creation from review findings or task breakdowns. Groups related findings into logical issues, applies labels, and produces issues with standard templates including summary, findings, and acceptance criteria. Designed to consume output from review-codebase or similar review skills.

pjt222/agent-almanac · 57 tokens

create-work-breakdown-structure

Create a Work Breakdown Structure (WBS) and WBS Dictionary from project charter deliverables. Covers hierarchical decomposition, WBS coding, effort estimation, dependency identification, and critical path candidates. Use after a project charter is approved, when planning a classic or waterfall project with defined…

pjt222/agent-almanac · 85 tokens