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 fatecannotbealtered/jira-cli --skill jira-cligit clone --depth 1 https://github.com/fatecannotbealtered/jira-cliWrote 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/fatecannotbealtered/jira-cli/jira-cli)<a href="https://agentmods.dev/skills/fatecannotbealtered/jira-cli/jira-cli"><img src="https://agentmods.dev/badge/skills/fatecannotbealtered/jira-cli/jira-cli/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/fatecannotbealtered/jira-cli/jira-cli"><img src="https://agentmods.dev/badge/skills/fatecannotbealtered/jira-cli/jira-cli.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.00050 | $0.03343 |
| Opus 5.5 | $0.00020 | $0.01337 |
| Sonnet 5.5 | $0.00010 | $0.00669 |
| Haiku 4.5 | $0.00005 | $0.00334 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
jira-cli
Jira Data Center CLI for AI agents. It supports self-hosted Jira Data Center / Jira Server style APIs, not Jira Cloud.
# Please install jira-cli and use it for Jira Data Center operations going forward.
# JSON is the default machine format; use --format text only for human-facing output.
npm install -g @fateforge/jira-cli
# Install the matching agent Skill.
npx skills add fatecannotbealtered/jira-cli -y -g
# Login and verify.
jira-cli --format text login
jira-cli doctor
When to use
Use this Skill for:
- Jira Data Center issue search, read, create, edit, transition, comments, worklogs, links, attachments, assignees, watchers, and votes.
- Batch issue operations over a set selected by explicit keys or JQL: bulk-create, backlog-move, bulk-assign, bulk-edit, and rank.
- Jira Data Center sprint, board, backlog, epic, project, user, and saved filter operations.
- JQL search or any workflow that needs Jira DC data from the terminal.
- Checking Jira CLI authentication, context, doctor diagnostics, audit behavior, self-update, or changelog.
Do not use this Skill for:
- Jira Cloud accountId/OAuth workflows.
- Generic project management advice without a Jira DC operation.
- Browser-only Jira tasks that require a logged-in web session and no CLI/API call.
- Administrative Jira configuration outside the authenticated user's normal permissions.
First steps
Before task commands, discover the current binary and environment:
jira-cli reference --compact
jira-cli context --compact
jira-cli doctor --compact
Use reference as the source of truth for commands, flags, output schema, error codes, exit codes, permission tiers, and blast radius. Do not rely on this Skill, README snippets, or --help for drift-prone command details.
Interpret doctor by reading .data.checks[]; relevant checks include config, auth, network, and version. The version check must satisfy metadata.requires.min_version in Skill frontmatter.
JSON contract
What ships with it
1 file 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.
- 1mo ago First seen · 236 lines · 50 tokens per session scan A f287e617d9db
jira-cli is a skill published in the GitHub repository fatecannotbealtered/jira-cli (5 stars, last pushed 4d ago), licensed MIT. It adds 50 tokens to every session and 3,343 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…