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 mrDesign-ww/vault-os --skill atlassian-admingit clone --depth 1 https://github.com/mrDesign-ww/vault-osWrote 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/mrdesign-ww/vault-os/atlassian-admin)<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>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.00098 | $0.03007 |
| Opus 5 | $0.00049 | $0.01503 |
| Sonnet 5 | $0.00020 | $0.00601 |
| Haiku 4.5 | $0.00010 | $0.00301 |
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.
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-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.
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
- Create user account:
admin.atlassian.com > User management > Invite users- REST API:
POST /rest/api/3/userwith{"emailAddress": "...", "displayName": "...","products": [...]}
- REST API:
- Add to appropriate groups:
admin.atlassian.com > User management > Groups > [group] > Add members - Assign product access (Jira, Confluence) via
admin.atlassian.com > Products > [product] > Access - Configure default permissions per group scheme
- Send welcome email with onboarding info
- NOTIFY: Relevant team leads of new member
- VERIFY: Confirm user appears active at
admin.atlassian.com/o/{orgId}/usersand can log in
User Deprovisioning
- 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}/propertyto find owned spaces/pages
- Jira:
- 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
- Jira projects:
- Remove from all groups:
admin.atlassian.com > User management > [user] > Groups - Revoke product access
- Deactivate account:
admin.atlassian.com > User management > [user] > Deactivate- REST API:
DELETE /rest/api/3/user?accountId={accountId}
- REST API:
- VERIFY: Confirm
GET /rest/api/3/user?accountId={accountId}returns"active": false - Document deprovisioning in audit log
- USE: Jira Expert to reassign any remaining issues
Group Management
- Create groups:
admin.atlassian.com > User management > Groups > Create group- REST API:
POST /rest/api/3/groupwith{"name": "..."} - Structure by: Teams (engineering, product, sales), Roles (admins, users, viewers), Projects (project-alpha-team)
- REST API:
- Define group purpose and membership criteria (document in Confluence)
- Assign default permissions per group
- Add users to appropriate groups
- VERIFY: Confirm group members via
GET /rest/api/3/group/member?groupName={name} - Regular review and cleanup (quarterly)
- USE: Confluence Expert to document group structure
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.
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.
- 8d ago First seen · 231 lines · 98 tokens per session scan A 44933862df55
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.
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…
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.
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…
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.
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.
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…