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 netresearch/jira-skill --skill jira-syntaxgit clone --depth 1 https://github.com/netresearch/jira-skillWrote 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/netresearch/jira-skill/jira-syntax)<a href="https://agentmods.dev/skills/netresearch/jira-skill/jira-syntax"><img src="https://agentmods.dev/badge/skills/netresearch/jira-skill/jira-syntax/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/netresearch/jira-skill/jira-syntax"><img src="https://agentmods.dev/badge/skills/netresearch/jira-skill/jira-syntax.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
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.00052 | $0.01158 |
| Opus 5.5 | $0.00021 | $0.00463 |
| Sonnet 5.5 | $0.00010 | $0.00232 |
| Haiku 4.5 | $0.00005 | $0.00116 |
Grade A, and why
jira-syntax 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 2d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What ships with it
8 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.
- 2d ago Changed 93f9d7b8020d
- 4d ago Changed 4d823c5534b5
- 17d ago Changed 035fc40cee04
- 18d ago Changed 7a69c0fd4ac9
- 25d ago Changed · +2 lines c2abdbcce804
- 28d ago Changed b0e4f46015d6
- 1mo ago Changed · +1 lines 09f67e4a976a
- 1mo ago Changed b9d8e79b95a3
- 1mo ago Changed · +1 lines edd8d858c42d
- 1mo ago First seen · 95 lines · 52 tokens per session scan A 75ca8c84b0e8
jira-syntax is a skill published in the GitHub repository netresearch/jira-skill (89 stars, last pushed today), with no licence file. It adds 52 tokens to every session and 1,158 once invoked, about $0.0002 per session on Opus 5.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.
Other skills, from other repositories
pm-skills
Use when coordinating project-delivery work across the 8 project-management sub-skills — sprint/velocity analytics, portfolio health, Jira/JQL, Confluence, Atlassian admin, templates, meeting analysis, team comms. Triggers on 'our sprints feel off', 'project health report', 'audit our Jira permissions', 'when will it…
c-jira
Manage Jira issues using jira (jira-cli). List and filter issues, create new tickets, transition issue status, manage sprints, and add comments — all from the terminal without opening a browser.
jira
Access Jira to search, summarize, and analyze tickets. Use when the user mentions a Jira ticket key (e.g. PROJ-1234), asks for a team digest, or wants to search/query Jira. Also use when the user wants to create issues, assign tickets, change ticket status, link issues, add comments, update fields, or do anything…
Jira QA Workflows
Run QA work in Jira like a professional, bug lifecycle and triage, JQL queries for testers, quality dashboards, sprint QA rituals, and REST API automation for bulk bug operations and reporting.
stale-ticket-triage
Replace the weekly "look at every ticket older than X days" meeting with a scheduled AI scan that picks close / snooze / keep per ticket plus a one-sentence reason, so a PM can bulk-approve in 90 seconds Monday morning.
atls
A command-line tool for working with Atlassian Jira, Confluence, and Bitbucket Server or Data Center. It includes rules for searching, reading, comparing, editing, and safely publishing Atlassian content.