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 ngocsangyem/MeowKit --skill jira-agilegit clone --depth 1 https://github.com/ngocsangyem/MeowKitWrote 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/ngocsangyem/meowkit/jira-agile)<a href="https://agentmods.dev/skills/ngocsangyem/meowkit/jira-agile"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/jira-agile/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/ngocsangyem/meowkit/jira-agile"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/jira-agile.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.00097 | $0.01216 |
| Opus 5 | $0.00048 | $0.00608 |
| Sonnet 5 | $0.00019 | $0.00243 |
| Haiku 4.5 | $0.00010 | $0.00122 |
Grade A, and why
mk:jira-agile 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mk:jira-agile
Forks to the jira-agile agent. Sprint operations require a numeric --board-id, not the project key. The agent resolves project name → board ID via agile board list --name "..." first.
Triggers
- "list sprints on board 'Team Alpha'"
- "add PROJ-123, PROJ-124 to sprint 42"
- "set 5 story points on PROJ-123"
- "rank PROJ-123 before PROJ-456 in backlog"
- "velocity for board 42"
- "create epic 'Auth Rewrite' in PROJ"
Examples
- Sprint create: "create sprint 'Sprint 21' on board 'Team Alpha' from 2026-05-13 to 2026-05-27"
- Epic populate: "add PROJ-123, PROJ-124, PROJ-125 to epic EPIC-1"
- Subtask: "create subtask of PROJ-123 — 'write integration test'"
Sprint commitment hooks (Agile-context-only — gated by agile-sprint-commitment.md 2/3 when loaded)
When tasks/contracts/sprint-state-{date}-sprint-{N}.md exists with status: active, wrap these operations:
sprint add KEY and sprint remove KEY (post-start)
- Read newest sprint-state file matching the active sprint
- Acquire
flockon the sprint-state file before any read-modify-write. YAML frontmatter append is non-atomic across shells; lock is the only mitigation - Per
agile-sprint-commitment.md2:AskUserQuestion"Reason for mid-sprint scope change?" — required free-text - Append
{ ts: <ISO ts>, action: add|remove, ticket: KEY, reason: <text> }toamendments:list - Release lock
- Proceed with the underlying
jira-as agile sprint add|removecall
If sprint-state contract is absent OR status: closed → skip the amendment ceremony silently.
sprint close
- Read
committed_tickets:from newest active sprint-state - Query each via
mk:jira-issue get KEY - For each non-terminal ticket (not Done/Cancelled/Won't-Do),
AskUserQuestion: "PROJ-X is in {status}. Carry over to next sprint? Drop? Mark as not delivered?" - Write closure summary:
status: closed,closed_at: <ts>,delivered: [...],carried_over: [...] - Proceed with the underlying
jira-as agile sprint closecall
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.
- 9d ago First seen · 91 lines · 97 tokens per session scan A c4246d2a38b4
mk:jira-agile is a skill published in the GitHub repository ngocsangyem/MeowKit (14 stars, last pushed 1mo ago), licensed MIT. It adds 97 tokens to every session and 1,216 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
jira-administration
Complete JIRA project and system administration including projects, automation rules, permissions, users, notifications, screens, issue types, and workflows. Use when managing project structure, automating work, configuring team access, or setting up issue tracking.
jira-service-management
Complete ITSM/ITIL workflow support for JSM - service desks, requests, SLAs, customers, approvals, knowledge base. Use when managing service desk requests, tracking SLAs, or handling customer operations.
jira-time-tracking
Time tracking, worklogs, and time reports. TRIGGERS: 'log time', 'time spent on', 'log hours', 'log work', 'worklog', 'time tracking', 'timesheet', 'how much time', 'time logged', 'time report', 'export timesheet', 'set estimate', 'remaining estimate', 'original estimate'. Use for time-related queries and operations…
jira-custom-fields
Custom field discovery and configuration. TRIGGERS: 'field ID for', 'what's the field ID', 'what is the field ID', 'list custom fields', 'what fields are available', 'what custom fields', 'show custom fields', 'customfield', 'find field', 'agile fields', 'configure agile fields', 'story points field'. Use for JIRA…
jira-issue-management
Core JIRA issue CRUD - create bugs/tasks/stories, get issue details, update fields, delete issues. TRIGGERS: 'show me [KEY]', 'get issue [KEY]', 'view issue', 'create a bug/task/story', 'update [KEY]', 'delete [KEY]', 'details of [KEY]', 'look up [KEY]', 'what's in [KEY]'. NOT FOR: epics (use jira-agile)…
jira-issue-relationships
Issue linking, blockers, and dependency analysis. TRIGGERS: 'what's blocking', 'what is blocking', 'is blocked by', 'link issues', 'link to', 'blockers for', 'depends on', 'clone issue', 'clone with', 'blocking chain', 'dependency graph', 'show dependencies', 'get blockers', 'relates to', 'duplicates'. Use for issue…