jira-assistant-setup

jira-assistant-setup is a command for Claude Code from grandcamel/JIRA-Assistant-Skills. It costs 16 tokens per session (897 once invoked), scanned C, original, MIT.

A setup guide for connecting JIRA Assistant Skills to a JIRA account. JIRA is a work-tracking system, and the connection uses an Atlassian API token, which is a credential for software access.

In plain words
What is it for?
Use it to check prerequisites, install the JIRA package, create an Atlassian API token, and configure the JIRA site and credentials.
Why use it?
It removes uncertainty around installing the required package, creating a token, and storing the JIRA connection details correctly.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the jira-assistant-skills plugin — 14 skills, 4 commands, 15 agents shipped together

Good fit Use it to check prerequisites, install the JIRA package, create an Atlassian API token, and configure the JIRA site and credentials.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/grandcamel/jira-assistant-skills/jira-assistant-setup
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.

Clone the repo
git clone --depth 1 https://github.com/grandcamel/JIRA-Assistant-Skills

Made for: Claude Code.

Or install jira-assistant-skills, the plugin that ships this one along with the rest of its 14 skills, 4 commands, 15 agents.

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-assistant-setup

README.md
[![agentmods](https://agentmods.dev/badge/commands/grandcamel/jira-assistant-skills/jira-assistant-setup/github.svg)](https://agentmods.dev/commands/grandcamel/jira-assistant-skills/jira-assistant-setup)
Your own site
<a href="https://agentmods.dev/commands/grandcamel/jira-assistant-skills/jira-assistant-setup"><img src="https://agentmods.dev/badge/commands/grandcamel/jira-assistant-skills/jira-assistant-setup/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-assistant-setup

Your own site · 80×15
<a href="https://agentmods.dev/commands/grandcamel/jira-assistant-skills/jira-assistant-setup"><img src="https://agentmods.dev/badge/commands/grandcamel/jira-assistant-skills/jira-assistant-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 897 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.00016 $0.00897
Opus 5 $0.00008 $0.00449
Sonnet 5 $0.00003 $0.00179
Haiku 4.5 $0.00002 $0.00090

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

Security

Grade C, and why

jira-assistant-setup scanned grade C with 1 finding 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.

Harvests environment variableshighData exfiltration

Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.

## Step 3: Collect Credentials
commands/jira-assistant-setup.md · 131 lines

How it starts

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

JIRA Assistant Setup

You are helping the user set up JIRA Assistant Skills. Guide them through the process conversationally.

Step 1: Check Prerequisites

First, verify the environment:

python3 --version

Check if the jira-as package is installed:

pip show jira-as 2>/dev/null && echo "Library installed" || echo "Library missing"

If the library is missing, install it from public PyPI:

pip install "jira-as>=1.1.3"

Step 2: Get API Token

Tell the user they need an API token from Atlassian. Offer to open the browser:

"To connect to JIRA, you'll need an API token from Atlassian. I can open the page where you can create one.

Would you like me to open https://id.atlassian.com/manage-profile/security/api-tokens ?"

If they agree, use:

python3 -c "import webbrowser; webbrowser.open('https://id.atlassian.com/manage-profile/security/api-tokens')"

Guide them:

  1. Click "Create API token"
  2. Name it "JIRA Assistant Skills" or similar
  3. Copy the token immediately (they won't see it again)

Step 3: Collect Credentials

Ask the user for their JIRA credentials:

  1. JIRA Site URL: Ask "What is your JIRA site URL? It should look like https://yourcompany.atlassian.net"

  2. Email: Ask "What email address do you use to log into JIRA?"

  3. API Token: Ask "Please paste your API token (I'll store it securely)"

  4. Profile Name: Ask "What would you like to name this profile? (default: production)"

Step 4: Configure Environment

Guide the user to set environment variables:

For bash/zsh (add to ~/.bashrc or ~/.zshrc):

export JIRA_SITE_URL="https://company.atlassian.net"
export JIRA_EMAIL="[email protected]"
export JIRA_API_TOKEN="their-token-here"

For PowerShell (add to profile):

$env:JIRA_SITE_URL="https://company.atlassian.net"
$env:JIRA_EMAIL="[email protected]"
$env:JIRA_API_TOKEN="their-token-here"

After setting, reload the shell:

source ~/.bashrc  # or source ~/.zshrc

Read the full file on GitHub · 131 lines

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 · 131 lines · 16 tokens per session scan C 0e31ac440fb3

Subscribe to this mod's changes

jira-assistant-setup is a command published in the GitHub repository grandcamel/JIRA-Assistant-Skills (46 stars, last pushed 3d ago), licensed MIT. It adds 16 tokens to every session and 897 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (harvests environment variables). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.