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 agentmods add skills/kv0906/pm-kit/jiranpx skills add kv0906/pm-kit --skill jiragit clone --depth 1 https://github.com/kv0906/pm-kitWrote 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/kv0906/pm-kit/jira)<a href="https://agentmods.dev/skills/kv0906/pm-kit/jira"><img src="https://agentmods.dev/badge/skills/kv0906/pm-kit/jira.svg" alt="Measured on agentmods" 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 | $0.00080 | $0.04401 |
| Opus 5 | $0.00040 | $0.02201 |
| Sonnet 5 | $0.00016 | $0.00880 |
| Haiku 4.5 | $0.00008 | $0.00440 |
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 5d 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 — 618 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/jira — Jira Integration
Bridge your PM-Kit vault with Jira issue tracking via the acli (Atlassian CLI) command-line tool. View boards, create/edit/transition issues, search via JQL, and sync Jira state with vault notes.
Prerequisites
- acli (Atlassian CLI):
brew install aclior download from https://bobswift.atlassian.net/wiki/spaces/ACLI - Jira Cloud or Server instance with API access
- Authentication configured via
acli jira auth login
Context
Today's date: !date +%Y-%m-%d
Config: @_core/config.yaml
Processing rules: @_core/PROCESSING.md
Active projects: !ls 01-index/*.md 2>/dev/null | sed 's|01-index/||;s|\.md||'
Input
User input: $ARGUMENTS
Sub-commands
Parse the first word of $ARGUMENTS to determine the sub-command:
| Input starts with | Sub-command | Purpose | Read/Write |
|---|---|---|---|
setup |
Setup | Guide installation + auth configuration | Config write |
board |
Board | Show board columns with issue counts | Read-only |
create |
Create | Create a Jira issue | Jira write + optional vault note |
status |
Status | Show details for a specific issue | Read-only |
move |
Move | Transition an issue to a new status | Jira write + vault note update |
edit |
Edit | Update issue fields | Jira write |
assign |
Assign | Assign an issue to someone | Jira write |
backlog |
Backlog | Show backlog items | Read-only |
search |
Search | Find issues via JQL or natural language | Read-only |
sprint |
Sprint | Show active sprint details | Read-only |
sync |
Sync | Pull Jira state into vault notes | Vault write (additive only) |
| (empty) | Help | Show help + quick status summary | Read-only |
Step 0: Connection Check
Before any sub-command (except setup), verify acli is installed and authenticated:
# 1. Check acli is installed
command -v acli &>/dev/null
# 2. Check auth works with a simple query
acli jira --action getServerInfo 2>/dev/null
If either fails:
Jira CLI (acli) is not connected yet.
Run `/jira setup` to install and configure — it takes about 2 minutes.
What ships with it
2 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.
- 5d ago First seen · 618 lines · 80 tokens per session scan A 6d7155005850
jira is a skill published in the GitHub repository kv0906/pm-kit (133 stars, last pushed 2mo ago), licensed MIT. It adds 80 tokens to every session and 4,401 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-30.
Other skills, from other repositories
critique-prd
Rubric-score a PRD pack (02 + 03) against the 7-dimension PM Brain rubric and run a 4-persona panel review. Returns scores, panel critiques, the single weakest section, a concrete rewrite, and P0/P1 fix lists. Use when: PRD review, score my PRD, rubric review, panel review, rewrite weakest section, critique-prd.
critique-agent
Pressure-test an existing product brief or PRD pack — find gaps, hidden assumptions, inconsistencies, and failure modes before stakeholder review. Use when: critique brief, critique PRD, devils advocate, red team, pressure test, find holes, what could go wrong, stress test the doc, pre-mortem.
interview-frameworks
Frameworks for user interviews, question design, and qualitative research. Use when conducting user interviews, designing interview guides, researching user needs, or gathering qualitative insights. Trigger on: 'create an interview guide', 'how do I interview users', 'customer discovery questions', 'user research…
query-datasets
Answer grounded yes/no questions about what exists in the 03-datasets/ example corpora (supporttickets, calltranscripts) using the local SQLite + FTS5 + vector hybrid index. Use when the user asks 'do/does [corpus] contain/mention/include/have requests for X?', 'any [corpus] about Y?', or similar factual queries over…
create-prd
Write the PRD pack (02-product-requirements.md + 03-success-metrics.md) on top of an approved product brief. Use when: PRD, product requirements, requirements doc, success metrics, spec writeup, shape the PRD.
create-product-brief
Write concise (2-page) product briefs to get buy-in before investing in full specs. Use when: product brief, one pager, feature brief, quick spec, feature proposal, pitch idea.