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 Dannykkh/skill-olympus --skill jiragit clone --depth 1 https://github.com/Dannykkh/skill-olympusWrote 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/dannykkh/skill-olympus/jira)<a href="https://agentmods.dev/skills/dannykkh/skill-olympus/jira"><img src="https://agentmods.dev/badge/skills/dannykkh/skill-olympus/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/dannykkh/skill-olympus/jira"><img src="https://agentmods.dev/badge/skills/dannykkh/skill-olympus/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.00028 | $0.01874 |
| Opus 5.5 | $0.00011 | $0.00750 |
| Sonnet 5.5 | $0.00006 | $0.00375 |
| Haiku 4.5 | $0.00003 | $0.00187 |
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.
This is a copy
91% identical to jira — 32 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira
Natural language interaction with Jira. Supports multiple backends.
Setup (최초 1회)
이 스킬은 config.json에 설정이 필요합니다.
config.json을 읽는다 (skills/jira/config.json또는 현재 CLI의 글로벌 스킬 경로)- 빈 필드가 있으면 현재 CLI의 질문 방식으로 사용자에게 질문한다
- 답변을
config.json에 저장한다 - 이후 실행 시에는
config.json에서 자동으로 읽는다
| 항목 | 설명 | 예시 |
|---|---|---|
jira_base_url |
Jira 인스턴스 URL | https://mycompany.atlassian.net |
default_project_key |
기본 프로젝트 키 (이슈 생성 시 자동 사용) | PROJ |
default_assignee |
기본 담당자 (본인 Jira 사용자명) | john.doe |
preferred_issue_types |
주로 사용하는 이슈 타입 목록 | ["Story", "Bug", "Task"] |
Setup 로직:
config.json 읽기
├─ jira_base_url 비어있음? → "Jira 인스턴스 URL을 입력해주세요 (예: https://mycompany.atlassian.net)"
├─ default_project_key 비어있음? → "기본 프로젝트 키를 입력해주세요 (예: PROJ, 건너뛰려면 Enter)"
├─ default_assignee 비어있음? → "기본 담당자(본인 Jira 사용자명)를 입력해주세요 (건너뛰려면 Enter)"
└─ 답변 수집 후 config.json에 저장 → 이후 자동 사용
모든 필드가 채워져 있으면 이 단계를 건너뜁니다.
Backend Detection
Run this check first to determine which backend to use:
1. Check if jira CLI is available:
→ Run: which jira
→ If found: USE CLI BACKEND
2. If no CLI, check for Atlassian MCP:
→ Look for mcp__atlassian__* tools
→ If available: USE MCP BACKEND
3. If neither available:
→ GUIDE USER TO SETUP
| Backend | When to Use | Reference |
|---|---|---|
| CLI | jira command available |
references/commands.md |
| MCP | Atlassian MCP tools available | references/mcp.md |
| None | Neither available | Guide to install CLI |
Quick Reference (CLI)
Skip this section if using MCP backend.
| Intent | Command |
|---|---|
| View issue | jira issue view ISSUE-KEY |
| List my issues | jira issue list -a$(jira me) |
| My in-progress | jira issue list -a$(jira me) -s"In Progress" |
| Create issue | jira issue create -tType -s"Summary" -b"Description" |
| Move/transition | jira issue move ISSUE-KEY "State" |
| Assign to me | jira issue assign ISSUE-KEY $(jira me) |
| Unassign | jira issue assign ISSUE-KEY x |
| Add comment | jira issue comment add ISSUE-KEY -b"Comment text" |
| Open in browser | jira open ISSUE-KEY |
| Current sprint | jira sprint list --state active |
| Who am I | jira me |
What ships with it
3 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.
- 1mo ago First seen · 226 lines · 28 tokens per session scan A 2db5d08bf345
jira is a skill published in the GitHub repository Dannykkh/skill-olympus (7 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 1,874 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to jira, differing in 32 lines, and is treated as a copy.
Other skills, from other repositories
factory-close
Close out a Linear issue — move to Done, add a closing comment, and clean up the local branch/worktree.
factory-submit
Move the current branch's Linear issue to "In Review".
audit-project
Audits the Claude Code configuration of a project against the dotforge template. Generates a report with score and gaps.
init-project
Quick-start Claude Code configuration. Auto-detects stack, asks 4 questions to understand the project, generates complete config.
domain-extract
Extract domain knowledge from existing project sources and generate domain rules. Also handles vault sync and domain listing.
rule-effectiveness
Cross-reference .claude/rules/ globs against git history to find inert rules and uncovered directories. Content quality and context cost are native — run /doctor prompt-audit and /skill-doctor for those.