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 agentmods add skills/mgiovani/cc-arsenal/jira-clinpx skills add mgiovani/cc-arsenal --skill jira-cligit clone --depth 1 https://github.com/mgiovani/cc-arsenalWrote 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/mgiovani/cc-arsenal/jira-cli)<a href="https://agentmods.dev/skills/mgiovani/cc-arsenal/jira-cli"><img src="https://agentmods.dev/badge/skills/mgiovani/cc-arsenal/jira-cli.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.00145 | $0.01322 |
| Opus 5 | $0.00072 | $0.00661 |
| Sonnet 5 | $0.00029 | $0.00264 |
| Haiku 4.5 | $0.00015 | $0.00132 |
Grade A, and why
jira-cli 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 5d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira CLI
Command reference and scripting patterns for jira-cli, the command-line tool for managing Jira issues, epics, and sprints without the web UI.
Prerequisites
These references assume jira on PATH is ankitpokhrel/jira-cli: a different tool can claim the same binary name. Before trusting any command below, run jira version once per session and confirm the output looks like this project (e.g. jira version 1.x.x with a Homepage: https://github.com/ankitpokhrel/jira-cli line). If it doesn't, stop and check which jira instead of guessing at flags.
For AI use, always add --plain (and usually --no-headers) to get parseable text output instead of the interactive table.
When to Use This Skill
Manual slash-command skill (/jira-cli): it does not auto-trigger on mentions of "jira" or "ticket". Invoke it directly for raw jira CLI commands (issues, epics, sprints) or scripting/automation. On tools that don't read Claude-Code frontmatter, disable-model-invocation is ignored: the /jira-cli phrasing itself is the manual-invocation signal there too.
Essential Commands
Curated top-7 for the most common operations. For anything else (filters, epic/sprint management, releases, output formats), load references/commands.md; don't try to recall the rest from memory.
# List recent issues (always use --plain for AI)
jira issue list --plain
# View issue details
jira issue view ISSUE-1 --plain
# Create an issue
jira issue create -tBug -s"Bug title" -yHigh -b"Description" --no-input
# Assign issue to yourself
jira issue assign ISSUE-1 $(jira me)
# Move issue to "In Progress"
jira issue move ISSUE-1 "In Progress"
# Add comment
jira issue comment add ISSUE-1 --comment "My comment"
# Add worklog
jira issue worklog add ISSUE-1 "2h" --comment "Implementation work"
Worked Examples
Confirm the CLI flavor before anything else:
$ jira version
jira version 1.5.1
Homepage: https://github.com/ankitpokhrel/jira-cli
A different jira version output (or a "command not found") means stop and resolve which jira before running any command from this skill.
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.
- 5d ago First seen · 111 lines · 145 tokens per session scan A 8e52d978abfc
jira-cli is a skill published in the GitHub repository mgiovani/cc-arsenal (7 stars, last pushed 5d ago), licensed MIT. It adds 145 tokens to every session and 1,322 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
ops-demo
CocoOps demo mode activator — populates .cocoplus/ops/demo/ with realistic mock data and sets cocoplus.toml [demo] enabled = true. Invoked via $ops demo.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…
acl-rule-analysis
Vendor-agnostic ACL and firewall rule analysis with shadowed rule detection, overly permissive rule identification, unused rule discovery, redundant rule flagging, and rule ordering optimization. Covers ACLs (Cisco/JunOS/EOS) and firewall policies (PAN-OS/FortiGate/CheckPoint).
add-analytics
Add Google Analytics 4 tracking to any project. Detects framework, adds tracking code, sets up events, and configures privacy settings.
agent-team-orchestration
Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team of 2+ agents with different specializations, (2) Defining task routing and lifecycle (inbox → spec → build → review → done), (3) Creating handoff protocols between agents, (4)…
agent-bom-enforce
Enforce security policies on MCP tool calls and block dangerous operations at runtime. Use when: "block risky calls", "apply policy", "proxy", "runtime protection", "policy enforcement", "intercept MCP calls".