agentmods.dev

jira-administration

jira-administration is a skill for Claude Code from upex-galaxy/agentic-qa-boilerplate. It costs 65 tokens per session (694 once invoked), scanned A, original, MIT.

A controlled workflow for administering Jira project components or moving an Atlassian instance to a different Jira address. It reads the current setup first and requires approval before making changes.

In plain words
What is it for?
Use it to reconcile Jira Components, synchronize components, or handle a changed or replaced Jira instance URL.
Why use it?
It reduces the risk of changing Jira configuration or credential-related settings without first checking their existing state.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: installed under .agents/ (shared by several agents); mentions AGENTS.md; mentions Codex.

not rated 21repo 7d ago A scan SkillSpector: pass 65 tokens original MIT

Good fit Use it to reconcile Jira Components, synchronize components, or handle a changed or replaced Jira instance URL.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/upex-galaxy/agentic-qa-boilerplate/jira-administration
View source ↗ upex-galaxy/agentic-qa-boilerplate upex-galaxy.github.io
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 upex-galaxy/agentic-qa-boilerplate --skill jira-administration
Clone the repo
git clone --depth 1 https://github.com/upex-galaxy/agentic-qa-boilerplate

Made for: Claude Code.

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 jira-administration

README.md
[![agentmods](https://agentmods.dev/badge/skills/upex-galaxy/agentic-qa-boilerplate/jira-administration/github.svg)](https://agentmods.dev/skills/upex-galaxy/agentic-qa-boilerplate/jira-administration)
Your own site
<a href="https://agentmods.dev/skills/upex-galaxy/agentic-qa-boilerplate/jira-administration"><img src="https://agentmods.dev/badge/skills/upex-galaxy/agentic-qa-boilerplate/jira-administration/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 jira-administration

Your own site · 80×15
<a href="https://agentmods.dev/skills/upex-galaxy/agentic-qa-boilerplate/jira-administration"><img src="https://agentmods.dev/badge/skills/upex-galaxy/agentic-qa-boilerplate/jira-administration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 694 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00065 $0.00694
Opus 5 $0.00032 $0.00347
Sonnet 5 $0.00013 $0.00139
Haiku 4.5 $0.00006 $0.00069

Measured 12d ago against content hash 90221ee618d7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

jira-administration 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 12d 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.

.agents/skills/jira-administration/SKILL.md · 39 lines

How it starts

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

Jira Administration

Mode routing

Choose exactly one mode and load only its reference.

Mode Legacy alias / trigger Reference
components jira-components, reconcile/sync Jira Components references/components.md
instance-migration jira-instance-migration, changed/repoint Jira instance references/instance-migration.md

If the mode is unclear, ask. Never combine both modes in one run.

Compact Rules

The sealed mutation contract. Binding on every run of either mode:

  • Exactly ONE mode per run: components (references/components.md) or instance-migration (references/instance-migration.md). Load only that mode's reference. Never combine the two, never fall through into the other.
  • Mode unclear → ASK. Do not infer one from a bare "fix Jira" / "sync Jira" request.
  • Load /acli before any Jira operation. Load other tool-owner skills only when the selected reference requires them.
  • Missing MCP or Jira credentials = HARD STOP (AGENTS.md Critical Rule #10). Name the exact env var, point at .env / .env.example, ask for an agent-session restart. No workaround, no partial run.
  • Read-first on every mutation: inspect the live state before authoring any plan. Nothing is created, applied, deleted, or repointed without the user's explicit approval given inside the same run.
  • components: derive and inspect → author the plan file → dry-run → WAIT for explicit approval → only then --apply.
  • instance-migration: resolve and confirm BOTH instances → audit and verify reachability → WAIT for explicit approval → only then change files or the acli session. That session lives at ~/.config/acli and is machine-global: re-login repoints every repo on the host, not just this one.
  • The Atlassian host lives in .agents/project.yaml → issue_tracker.atlassian_url and NOWHERE else locally. A stale ATLASSIAN_URL in .env or the process environment is contamination to DELETE, never to update — a second copy is what goes stale.
  • Template-repo carve-out: if .agents/project.yaml → project.project_name is null, the repo is an un-onboarded template. Leave atlassian_url and project_key null, say so in the report, and never manufacture a commit to hide the emptiness.
  • Run only the selected reference's verification steps. Never run the other mode's.
  • Forward $ARGUMENTS unchanged.

Read the full file on GitHub · 39 lines

Files

What ships with it

2 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. 12d ago First seen · 39 lines · 65 tokens per session scan A 90221ee618d7

Subscribe to this mod's changes

jira-administration is a skill published in the GitHub repository upex-galaxy/agentic-qa-boilerplate (21 stars, last pushed 7d ago), licensed MIT. It adds 65 tokens to every session and 694 once invoked, about $0.0003 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-30.

Claude CodeProject managementagent-skillsagentic-workflowagentskillsai-agentsboilerplate
Related

Other skills, from other repositories

discover-product

Run a multi-round discovery (persona / pain / JTBD / scenario / MVP / assumptions) and write DISCOVERY.md.

kohj1018/agentic-dev-harness · 28 tokens

accept-milestone

Use ONLY when the user explicitly types $accept-milestone . Do not trigger implicitly from generic phrasing.

kohj1018/agentic-dev-harness · 32 tokens

on-call-best-practices

Manage on-call rotations with sustainable practices, fair scheduling, and effective handoffs. Use this skill when setting up on-call, improving on-call experience, or managing rotations. Activate when: on-call, pagerduty, rotation, schedule, handoff, on-call burden, being paged, night pages, weekend on-call, on-call…

latestaiagents/agent-skills · 77 tokens

onboarding-checklist

Create comprehensive onboarding plans that set new hires up for success. Use this skill when preparing for new employee arrivals, improving onboarding processes, or building role-specific onboarding. Activate when: onboarding, new hire, first day, new employee, orientation, employee onboarding, 30-60-90.

latestaiagents/agent-skills · 63 tokens

standup

(forwward) Writes outcome-first status updates leaders actually read, with options + lean recommendation for blockers. Use when the user says "standup", "status report", "progress update", "weekly update", "executive summary", "update on [project]", or pastes project details without specifying intent. Reads git log…

iankiku/forwward-teams · 97 tokens

meeting

(forwward) Turns transcripts, rough notes, or voice memos into a clean summary with decisions, action items (owner + deadline), and open questions. Use when the user pastes unstructured notes or asks "summarize this meeting", "meeting notes", "what were the action items", "write up from this call", "debrief", "what…

iankiku/forwward-teams · 105 tokens