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 peteroden/jira-and-gitlab-skills --skill jiragit clone --depth 1 https://github.com/peteroden/jira-and-gitlab-skillsWrote 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/peteroden/jira-and-gitlab-skills/jira)<a href="https://agentmods.dev/skills/peteroden/jira-and-gitlab-skills/jira"><img src="https://agentmods.dev/badge/skills/peteroden/jira-and-gitlab-skills/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/peteroden/jira-and-gitlab-skills/jira"><img src="https://agentmods.dev/badge/skills/peteroden/jira-and-gitlab-skills/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.00087 | $0.01986 |
| Opus 5 | $0.00044 | $0.00993 |
| Sonnet 5 | $0.00017 | $0.00397 |
| Haiku 4.5 | $0.00009 | $0.00199 |
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 11d 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prerequisites
The script at .github/skills/jira/jira requires python3 (3.6+).
Environment variables (must be set before running any command):
| Variable | When required | Purpose |
|---|---|---|
JIRA_BASE_URL |
Always | Jira instance URL (e.g., https://company.atlassian.net) |
JIRA_USER_EMAIL |
Cloud | Account email for basic auth |
JIRA_API_TOKEN |
Cloud | API token paired with email |
JIRA_PAT |
Server/DC | Personal access token (bearer auth) |
Auth is auto-detected: if JIRA_PAT is set → Server/DC bearer auth. Otherwise → Cloud basic auth with email + token.
If a command fails with JIRA_BASE_URL is not set, verify the env vars are exported in the current shell.
Output Modes
All read commands (search, get, comments) support a --fields flag that extracts specific fields using dot-notation, outputting tab-separated values instead of raw JSON. Always use --fields by default to keep output concise:
.github/skills/jira/jira search 'assignee = currentUser()' --fields key,fields.summary,fields.status.name
.github/skills/jira/jira get PROJ-123 --fields key,fields.summary,fields.status.name,fields.assignee.displayName
.github/skills/jira/jira comments PROJ-123 PROJ-456 --fields _issue,author.displayName,created,body
For lists, output includes a header row. For single items, output is field: value per line. Nested fields use dot-notation (e.g. fields.status.name). Omit --fields only when the full JSON is needed.
Command Reference
All commands use the full path: .github/skills/jira/jira <command> [args...]
| Command | Purpose | Syntax |
|---|---|---|
search |
Find issues via JQL | .github/skills/jira/jira search '<jql>' [max_results] |
get |
Fetch a single issue | .github/skills/jira/jira get <ISSUE-KEY> |
create |
Create a new issue | .github/skills/jira/jira create '<json>' |
update |
Update issue fields | .github/skills/jira/jira update <ISSUE-KEY> '<json>' |
transition |
Change issue status | .github/skills/jira/jira transition <ISSUE-KEY> '<status>' |
comment |
Add a comment | .github/skills/jira/jira comment <ISSUE-KEY> '<body>' |
comments |
List comments on issues | .github/skills/jira/jira comments <ISSUE-KEY> [ISSUE-KEY ...] |
fields |
Discover issue types & fields | .github/skills/jira/jira fields <PROJECT-KEY> [issue-type-id] |
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.
- 11d ago First seen · 195 lines · 87 tokens per session scan A 9af4708e6e6b
jira is a skill published in the GitHub repository peteroden/jira-and-gitlab-skills (5 stars, last pushed 6mo ago), licensed MIT. It adds 87 tokens to every session and 1,986 once invoked, about $0.0004 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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.