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.
git clone --depth 1 https://github.com/grandcamel/JIRA-Assistant-SkillsWrote 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/commands/grandcamel/jira-assistant-skills/jira-assistant-setup)<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.
<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>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.00016 | $0.00891 |
| Opus 5.5 | $0.00006 | $0.00356 |
| Sonnet 5.5 | $0.00003 | $0.00178 |
| Haiku 4.5 | $0.00002 | $0.00089 |
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 1mo 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 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>=2,<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:
- Click "Create API token"
- Name it "JIRA Assistant Skills" or similar
- Copy the token immediately (they won't see it again)
Step 3: Collect Credentials
Ask the user for their JIRA credentials:
-
JIRA Site URL: Ask "What is your JIRA site URL? It should look like https://yourcompany.atlassian.net"
-
Email: Ask "What email address do you use to log into JIRA?"
-
API Token: Ask "Please paste your API token (I'll store it securely)"
-
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
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.
- 1mo ago Changed 079a61615263
- 1mo ago First seen · 131 lines · 16 tokens per session scan C 0e31ac440fb3
jira-assistant-setup is a command published in the GitHub repository grandcamel/JIRA-Assistant-Skills (48 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 891 once invoked, about $0.0001 per session on Opus 5.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.
Other commands, from other repositories
onboard
You are an expert onboarding specialist and knowledge transfer architect with deep experience in remote-first organizations, technical team integration, and accelerated learning methodologies. Your role is to ensure smooth, comprehensive onboarding that transforms new team members into productive contributors while…
set-tracker
Set the issue tracker for the current project.
workflow-design
Exécuter la phase de Conception (Solutioning) - spécification technique et architecture.
sprint
Équipe de Développement Sprint - Implémentation parallèle de stories utilisant les Agent Teams.
daily-standup
Génération Résumé Daily Stand-up.
speckit.companion.living-move
Move a living spec between central and colocated storage — file, tiers, and registry together (opt-in, reversible).