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 adampoit/ai --skill jiragit clone --depth 1 https://github.com/adampoit/aiWrote 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/adampoit/ai/jira)<a href="https://agentmods.dev/skills/adampoit/ai/jira"><img src="https://agentmods.dev/badge/skills/adampoit/ai/jira/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/adampoit/ai/jira"><img src="https://agentmods.dev/badge/skills/adampoit/ai/jira.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.00051 | $0.00360 |
| Opus 5.5 | $0.00020 | $0.00144 |
| Sonnet 5.5 | $0.00010 | $0.00072 |
| Haiku 4.5 | $0.00005 | $0.00036 |
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 1mo 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.
What it actually says
Jira
Search Jira issues and read issue details with jira.
jira issue list --jql 'text ~ "workflow runner failure"' --paginate 0:10 --raw
Search Issues
Search with free text:
jira issue list "build failure" --paginate 0:10 --raw
Search with explicit JQL:
jira issue list --jql "project = PROJ AND statusCategory != Done ORDER BY updated DESC" --paginate 0:10 --raw
Common options:
--jql: Raw JQL query- positional text: Free-text query
--paginate 0:10: Offset/limit style pagination--raw: JSON output for deterministic parsing
Read Issue
Read one issue with comments:
jira issue view PROJ-1234 --comments 20 --raw
Read plain text output (non-JSON):
jira issue view PROJ-1234 --comments 5 --plain
Guardrails
Prefer read-only commands in this skill:
jira issue list ...jira issue view ...
Avoid mutating commands unless the user explicitly requests edits (for example jira issue create, jira issue edit, jira issue delete, jira issue move, jira issue assign, jira issue comment add).
Use --raw whenever machine-readable output is needed.
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.
- 1mo ago First seen · 59 lines · 51 tokens per session scan A 7391cf1c0854
jira is a skill published in the GitHub repository adampoit/ai (2 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 360 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-31.
Other skills, from other repositories
openspec-bulk-archive-change
Archive multiple completed OpenSpec changes at once. Use when archiving several parallel changes. Also use for a plural archive request - "openspec bulk-archive", "opsx bulk-archive", "openspec archive all", or "openspec archive these changes".
openspec-bulk-apply-change
Use when multiple active OpenSpec changes should be applied concurrently in isolated worktrees with delegated verification and no merge.
openspec-new-change
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach. Also use when the user says "openspec new change" or "opsx new".
openspec-archive-change
Archive a completed OpenSpec change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete. Also use when the user says "openspec archive" or "opsx archive".
init-agent-sync
Initializes the AGENTSYNC.md hub for AI agent coordination and task tracking.
wrap-phase
Wraps up a development phase by cleaning AGENTSYNC.md, summarizing work, and committing changes.