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 tkolleh/skills --skill jiragit clone --depth 1 https://github.com/tkolleh/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/skills/tkolleh/skills/jira)<a href="https://agentmods.dev/skills/tkolleh/skills/jira"><img src="https://agentmods.dev/badge/skills/tkolleh/skills/jira.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.00142 | $0.01914 |
| Opus 5 | $0.00071 | $0.00957 |
| Sonnet 5 | $0.00028 | $0.00383 |
| Haiku 4.5 | $0.00014 | $0.00191 |
Grade A, and why
jira 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.
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira CLI
Bridge natural language to jira (jira-cli). Portable across users, projects, Cloud/Server/DC — never hardcode project keys, usernames, servers, or board IDs.
Work phases in order for each request. Skip only phases marked optional when their precondition is unmet.
Prerequisites (fail fast)
command -v jira >/dev/null || { echo "jira CLI missing — install ankitpokhrel/jira-cli"; exit 1; }
jira me >/dev/null 2>&1 || { echo "jira not authenticated — run: jira init"; exit 1; }
On failure: report the exact fix (brew install jira-cli / jira init) and STOP. Do not invent issue keys or statuses.
Optional tools: jq (JSON field extract), pandoc (Markdown→Jira wiki for descriptions/comments). If missing, prefer --plain text or pass simple plain text bodies.
Phase 1 — Resolve context
Establish active issue key, project, and acting user before writes.
- Issue key — Prefer explicit key in the user message (
[A-Z][A-Z0-9]+-\d+). Else parse current git branch (feat/PROJ-123-…,PROJ-123-…). Else search (Phase 2). Never invent keys. - Project — Explicit
-p KEY/ user text wins. Else default from config (jirauses~/.config/.jira/.config.yml, override withJIRA_CONFIG_FILE). For another project always pass-p KEYor JQLproject = KEY. - User —
ME=$(jira me)for "me" / "my". Assignees accept email or exact display name; self-assign:jira issue assign KEY "$(jira me)". - Session memory (optional) — If a memory tool exists, read/write active key as
JIRA_ACTIVE_KEY. If none, keep the key in conversation only. Do not require serena/openmemory.
Completion: you can name the target key and/or project, or you are about to search with an explicit JQL/filter plan.
Phase 2 — Read (prefer structured output)
| Goal | Command |
|---|---|
| View one issue | jira issue view KEY --plain (human) or jira issue view KEY --raw (JSON) |
| List / search | jira issue list [flags] --plain or --raw |
| My open work | jira issue list -a"$(jira me)" -s~Done --plain --columns key,status,summary,priority |
| Recent | jira issue list --history --plain |
| Cross-project JQL | jira issue list -q'project IS NOT EMPTY AND …' --plain |
| Sprint issues | jira sprint list --current --plain (needs board in config) |
| Epics | jira epic list --table --plain |
What ships with it
5 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 · 141 lines · 142 tokens per session scan A 11e553223f0b
jira is a skill published in the GitHub repository tkolleh/skills (1 stars, last pushed 2d ago), licensed MIT. It adds 142 tokens to every session and 1,914 once invoked, about $0.0007 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-31.
Other skills, from other repositories
syndic
Gère un parc de copropriétés en France avec vue portfolio consolidée. Couvre administration, comptabilité (décret 2005, plan comptable copro, 5 annexes), assemblées générales (convocation, PV, notification), appels de fonds, travaux, fournisseurs, recouvrement d'impayés et transition de syndic. Maîtrise les majorités…
implement-improvements
Validate improvements from .turbo/improvements.md, recommend a working set tailored to what's in the backlog, and run one lane: direct fixes, investigation, or planned work. One lane per session. Use when the user asks to "implement improvements", "work on improvements", "address improvements", "process improvement…
note-improvement
Capture an out-of-scope improvement opportunity so it doesn't get lost. Use when the user asks to "note improvement", "save improvement", "track this for later", "remember this improvement", "note this idea", "log improvement", "backlog this", or "park this idea". Also invoke proactively when noticing something…
create-issue
Create a GitHub issue with a drafted title and body. Use when the user asks to "create an issue", "file an issue", "open an issue", "submit an issue", "report a bug", "file a bug report", "file a feature request", or "file a design proposal".
pick-next-issue
Fetch and rank open GitHub issues by community engagement, present the top 3 candidates, and plan implementation for the selected issue. Use when the user asks to "pick next issue", "next issue", "which issue should I work on", "top issues", "most popular issues", "prioritize issues", or "what should I work on next".
split-and-ship
Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".