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-jsmgit 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-jsm)<a href="https://agentmods.dev/skills/ngocsangyem/meowkit/jira-jsm"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/jira-jsm/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-jsm"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/jira-jsm.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.00104 | $0.00672 |
| Opus 5.5 | $0.00042 | $0.00269 |
| Sonnet 5.5 | $0.00021 | $0.00134 |
| Haiku 4.5 | $0.00010 | $0.00067 |
Grade A, and why
mk:jira-jsm 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.
What it actually says
mk:jira-jsm
Forks to the jira-jsm agent. Service Management (JSM) operations — service desks, requests, SLAs, customers, organizations, queues, approvals, request types.
Triggers
- "create JSM request in service desk 'IT Support'"
- "list service desks"
- "SLA status for KEY-123"
- "approve request KEY-123"
- "list queue 'Tier 1 Support'"
- "add comment to JSM request KEY-123" (agent will confirm internal vs public)
Examples
- Get service desk status: "show me the queues for service desk 'IT Support'"
- Customer-facing comment: "add public comment to KEY-123: ''" → agent confirms internal-vs-public per safety-framework.
Required Permissions
JSM-licensed tenant + agent or admin role. Insufficient permission → exit code 3.
Limitations
- 8 sub-domains, ~45 verbs total — see
jira-as jsm <sub-domain> --helpfor the authoritative flag list. - Internal-vs-public comments are a privacy concern; the agent enforces explicit confirmation before posting customer-facing content.
See also
- Agent:
../../agents/jira-jsm.md - Shared:
../jira/references/{install-and-auth,cli-idioms,safety-framework}.md - Domain refs:
references/decision-tree.md— when to usemk:jira-jsmvsmk:jira-{issue,lifecycle,collaborate}etc.references/itil-workflows.md— ITIL 4 process implementations (incident / service-request / problem / change management)
- Peer leaves:
mk:jira-collaborate(internal-vs-public discipline applies on JSM tickets too),mk:jira-lifecycle(patterns/jsm-request-workflow.md),mk:jira-admin(request-type / queue config)
Gotchas
- (none yet)
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.
- 1mo ago First seen · 66 lines · 104 tokens per session scan A d9ba66751291
mk:jira-jsm is a skill published in the GitHub repository ngocsangyem/MeowKit (15 stars, last pushed 3mo ago), licensed MIT. It adds 104 tokens to every session and 672 once invoked, about $0.0004 per session on Opus 5.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
customer-support-expert
Build comprehensive customer support systems including ticketing, knowledge management, SLA tracking, and customer satisfaction analytics. Use when the user mentions helpdesk or service desk, ticketing, SLA targets, knowledge bases, escalation workflows, CSAT/NPS, or customer success operations.
Jira QA Workflows
Run QA work in Jira like a professional, bug lifecycle and triage, JQL queries for testers, quality dashboards, sprint QA rituals, and REST API automation for bulk bug operations and reporting.
integration-rule-engine
A declarative routing engine that turns ticket / error attributes (reporter, label, project, area path, error class, environment) into a tag + AI agent + priority assignment, so cross-source workflows ("security tickets always go to the OWASP reviewer") stay out of code and in user-editable rules.
stale-ticket-triage
Replace the weekly "look at every ticket older than X days" meeting with a scheduled AI scan that picks close / snooze / keep per ticket plus a one-sentence reason, so a PM can bulk-approve in 90 seconds Monday morning.
brace-sla
Design SLA framework -- response time targets, resolution time targets, tier definitions, and breach escalation process. Use when asked to "define our SLAs", "what response times should we commit to", "build a support tier structure", or "set up SLA monitoring".
atls
A command-line tool for working with Atlassian Jira, Confluence, and Bitbucket Server or Data Center. It includes rules for searching, reading, comparing, editing, and safely publishing Atlassian content.