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 AlirezaSoltaniJazi/Skillnir --skill jiragit clone --depth 1 https://github.com/AlirezaSoltaniJazi/SkillnirWrote 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/alirezasoltanijazi/skillnir/jira)<a href="https://agentmods.dev/skills/alirezasoltanijazi/skillnir/jira"><img src="https://agentmods.dev/badge/skills/alirezasoltanijazi/skillnir/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/alirezasoltanijazi/skillnir/jira"><img src="https://agentmods.dev/badge/skills/alirezasoltanijazi/skillnir/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.00136 | $0.02585 |
| Opus 5 | $0.00068 | $0.01293 |
| Sonnet 5 | $0.00027 | $0.00517 |
| Haiku 4.5 | $0.00014 | $0.00259 |
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 9d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Before You Start
Read LEARNED.md first. It holds corrections, preferences, and per-repo conventions (the confirmed project key, the team's review status name) discovered in previous sessions. Every rule there overrides defaults in this skill.
Announce skill usage. Say "Using: jira skill" at the very start of your response before doing any work.
Preflight once per session: run acli jira auth status. It reports the authenticated site and account — use that site for every issue URL; never hardcode a domain. If not authenticated, stop and tell the user to run acli jira auth login — never guess credentials.
When to Use
- Creating a Jira ticket as a child under an Epic or Story
- Searching / listing issues (find a parent, "my open issues", by summary)
- Viewing an issue's fields
- Transitioning status (e.g. to the team's review or done state)
- Commenting on an issue (e.g. attaching a PR/MR link)
- Editing summary / assignee / labels on an existing issue
Do NOT Use
- Raising PRs / MRs, creating branches, or commits — use github (GitHub) or gitlab (GitLab). This skill never touches git branches.
- Putting file paths, code, function/class names, or internal identifiers into a Jira description — those belong in the PR/MR. Keep Jira text non-technical.
- Skill-system meta-rules (SKILL.md structure, LEARNED.md format) — use skillnir.
Access & Conventions
| Fact | Value |
|---|---|
| Tool | acli jira workitem … (Atlassian CLI) |
| Site | Whatever acli jira auth status reports — never hardcode |
| Issue URL | <site>/browse/<KEY>-<n> |
| Project key | Auto-detect per repo — never hardcode (see below) |
| Review status | Instance-specific (e.g. "In Review", "In Code Review") — detect from LEARNED.md or ask, then record |
| Descriptions | Non-technical: user-visible problem, repro, expected vs actual, plain-language cause/fix |
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.
- 9d ago First seen · 143 lines · 136 tokens per session scan A 3e3573208ce8
jira is a skill published in the GitHub repository AlirezaSoltaniJazi/Skillnir (7 stars, last pushed 1mo ago), licensed MIT. It adds 136 tokens to every session and 2,585 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
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.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.