Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/FortiumPartners/ensemblenpx agentmods add skills/fortiumpartners/ensemble/managing-jira-issuesWrote 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/fortiumpartners/ensemble/managing-jira-issues)<a href="https://agentmods.dev/skills/fortiumpartners/ensemble/managing-jira-issues"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/managing-jira-issues/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/skills/fortiumpartners/ensemble/managing-jira-issues"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/managing-jira-issues.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.00041 | $0.02162 |
| Opus 5 | $0.00020 | $0.01081 |
| Sonnet 5 | $0.00008 | $0.00432 |
| Haiku 4.5 | $0.00004 | $0.00216 |
Grade A, and why
managing-jira-issues 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira Integration Skill
Purpose: Issue management for Jira Cloud using the jira CLI with JSON output optimized for LLM agents.
Tool: jira CLI (installed globally via npm link from ~/utils/atlassian)
Table of Contents
- Prerequisites
- Decision Tree
- Quick Command Reference
- Pattern Recognition - Auto-Invocation
- Workflow Examples
- Error Handling
- JSON Output Handling
- Comparison: Quick Read vs Fetch
- Version History
Prerequisites
Verify Installation
# Check CLI installed
jira --version # Expects: 1.0.0
Authentication
Config location: ~/utils/atlassian/.env
ATLASSIAN_CLOUD_ID=your-cloud-id
[email protected]:API_TOKEN
ATLASSIAN_SITE_URL=https://your-site.atlassian.net
Get API token from: https://id.atlassian.com/manage-profile/security/api-tokens
Decision Tree
Issue Operations
User wants to...
├── View issue details
│ └── jira issues read <ISSUE-KEY>
├── List recent issues
│ └── jira issues list [--limit N] [--project KEY]
├── Search issues
│ └── jira issues search "query" [--project KEY]
├── Create new issue
│ └── jira issues create "Title" --project KEY [options]
├── Update existing issue
│ └── jira issues update <ISSUE-KEY> [--status|--assignee|--priority]
├── Fetch complete hierarchy
│ └── jira issues fetch <ISSUE-KEY> --output ./spec
└── Get available transitions
└── jira issues transitions <ISSUE-KEY>
Metadata Operations
User wants to...
├── List projects
│ └── jira projects list
└── List users
└── jira users list [--query NAME]
Comments
├── Add comment
│ └── jira comments create <ISSUE-KEY> --body "Comment text"
└── List comments
└── jira comments list <ISSUE-KEY>
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.
- 6d ago First seen · 326 lines · 41 tokens per session scan A 8f6542427730
managing-jira-issues is a skill published in the GitHub repository FortiumPartners/ensemble (12 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 2,162 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
github-operations
GitHub CLI operations for issues, PRs, milestones, and Projects v2. Covers gh commands, REST API patterns, and automation scripts. Use when managing GitHub issues, PRs, milestones, or Projects with gh.
bmad-check-implementation-readiness
Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".
bmad-create-story
Creates a dedicated story file with all the context the agent will need to implement it later. Use when the user says "create the next story" or "create story [story identifier]".
bmad-retrospective
Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]".
bmad-generate-project-context
Create project-context.md with AI rules. Use when the user says "generate project context" or "create project context".
bmad-create-epics-and-stories
Break requirements into epics and user stories. Use when the user says "create the epics and stories list".