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/code-and-sorts/awesome-copilot-agents/jira-clinpx skills add Code-and-Sorts/awesome-copilot-agents --skill jira-cligit clone --depth 1 https://github.com/Code-and-Sorts/awesome-copilot-agentsWrote 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/code-and-sorts/awesome-copilot-agents/jira-cli)<a href="https://agentmods.dev/skills/code-and-sorts/awesome-copilot-agents/jira-cli"><img src="https://agentmods.dev/badge/skills/code-and-sorts/awesome-copilot-agents/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 | $0.00060 | $0.01836 |
| Opus 5 | $0.00030 | $0.00918 |
| Sonnet 5 | $0.00012 | $0.00367 |
| Haiku 4.5 | $0.00006 | $0.00184 |
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 — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira CLI
Interact with Atlassian Jira from the command line using jira-cli.
When to Use
- User asks to create, view, edit, or search Jira issues/tickets
- User needs to transition issues through workflow states (To Do → In Progress → Done)
- User wants to manage sprints, epics, or boards
- User needs to assign issues, add comments, or log work time
- User asks about their current tasks or sprint progress
Prerequisites
- Install jira-cli:
brew install ankitpokhrel/jira-cli/jira-cli(macOS) or download from releases - Set API token:
export JIRA_API_TOKEN="your-token" - Initialize:
jira initand follow prompts
Issue Commands
List Issues
# List issues in current project
jira issue list
# List my assigned issues
jira issue list -a$(jira me)
# List issues by status
jira issue list -s"In Progress"
# List high priority issues
jira issue list -yHigh
# List issues with multiple filters
jira issue list -a$(jira me) -s"To Do" -yHigh --created week
# List issues with raw JQL
jira issue list -q "project = PROJ AND status = 'In Progress'"
# Plain text output for scripting
jira issue list --plain --columns key,summary,status --no-headers
Create Issues
# Interactive issue creation
jira issue create
# Create with all options specified
jira issue create -tBug -s"Login button not working" -b"Description here" -yHigh --no-input
# Create a story
jira issue create -tStory -s"Add user authentication" -yMedium
# Create with labels and components
jira issue create -tTask -s"Update dependencies" -lmaintenance -l"tech-debt" -Cbackend
# Create and assign to self
jira issue create -tBug -s"Fix crash on startup" -a$(jira me) --no-input
View Issues
# View issue details
jira issue view ISSUE-123
# View with comments
jira issue view ISSUE-123 --comments 10
# View in plain text
jira issue view ISSUE-123 --plain
# Open issue in browser
jira open ISSUE-123
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 · 305 lines · 60 tokens per session scan A 8632f21ad80d
jira-cli is a skill published in the GitHub repository Code-and-Sorts/awesome-copilot-agents (564 stars, last pushed 4mo ago), licensed CC0-1.0. It adds 60 tokens to every session and 1,836 once invoked, about $0.0003 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-30.
Other skills, from other repositories
code-review
Use when user wants code reviewed for correctness, style, bugs, and maintainability. Triggers on: review code, code review, check PR, 審查程式碼, 檢查程式碼. Produces severity-classified findings with a verdict. Do NOT use for security-focused audit (prefer security-audit) or SQL-focused review (prefer sql-review).
plan
Use when user needs a phased implementation plan with requirements, file impact, risks, and alternatives before coding — including clarifying vague or ambiguous requirements first. Triggers on: plan, how should we build, unclear requirements, 規劃, 幫我想方案. Produces a structured plan document. Do NOT use for atomic task…
security-audit
Use when user needs an OWASP-focused security audit of Java web code — injection, auth, access control, and configuration review. Triggers on: security audit, OWASP, vulnerability check, 資安審查, 有沒有漏洞. Produces severity-classified security findings. Do NOT use for general code review (prefer code-review) or SQL-only…
sql-review
Use when user needs SQL reviewed — queries for injection risks, performance, and index strategy, or DDL/DML migration scripts for rollback safety, data-loss risk, lock impact, and backward compatibility. Triggers on: review SQL, slow query, review migration, SQL 審查, 看 migration. Produces severity-classified findings…
verify
Use when checking whether an implementation actually meets its acceptance criteria — derive the checks, bind each to a runnable command, execute, and gate pass/fail so a build loop has an objective exit condition. Triggers on: verify, does it pass, acceptance check, definition of done, test cases, what to test, 驗證…
debug
Use when user reports a bug, error, exception, or unexpected behavior needing root cause analysis and minimal fix. Triggers on: debug this, why does this fail, root-cause this, 除錯, 找 bug. Performs systematic isolation and minimal fix. Do NOT use for feature requests (prefer implement) or known simple typos (prefer…