agentmods.dev

mk:jira-jsm

mk:jira-jsm is a skill for Claude Code from ngocsangyem/MeowKit. It costs 104 tokens per session (672 once invoked), scanned A, original, MIT.

A tool for Jira Service Management, the Jira edition used by support teams to handle customer requests, queues, approvals, and service targets.

In plain words
What is it for?
Manage service desks, request types, customer requests, customers, organisations, queues, service-level agreements, and approvals.
Why use it?
It brings support-desk work into the same Jira environment and helps distinguish internal notes from customer-facing replies.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: agent in frontmatter.

not rated 14repo 1mo ago A scan 104 tokens original MIT

Good fit Manage service desks, request types, customer requests, customers, organisations, queues, service-level agreements, and approvals.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ngocsangyem/meowkit/jira-jsm
View source ↗ ngocsangyem/MeowKit docs.meowkit.dev
Install

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.

Any agent
npx skills add ngocsangyem/MeowKit --skill jira-jsm
Clone the repo
git clone --depth 1 https://github.com/ngocsangyem/MeowKit

Made for: Claude Code.

Wrote 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.

agentmods badge for mk:jira-jsm

README.md
[![agentmods](https://agentmods.dev/badge/skills/ngocsangyem/meowkit/jira-jsm/github.svg)](https://agentmods.dev/skills/ngocsangyem/meowkit/jira-jsm)
Your own site
<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.

agentmods 80×15 button for mk:jira-jsm

Your own site · 80×15
<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>
Per session 104 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 672 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00104 $0.00672
Opus 5 $0.00052 $0.00336
Sonnet 5 $0.00021 $0.00134
Haiku 4.5 $0.00010 $0.00067

Measured 8d ago against content hash d9ba66751291, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

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 8d 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.

.claude/skills/jira-jsm/SKILL.md · 66 lines

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> --help for 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 use mk:jira-jsm vs mk: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)
Files

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.

Changes

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.

  1. 8d ago First seen · 66 lines · 104 tokens per session scan A d9ba66751291

Subscribe to this mod's changes

mk:jira-jsm is a skill published in the GitHub repository ngocsangyem/MeowKit (14 stars, last pushed 1mo ago), licensed MIT. It adds 104 tokens to every session and 672 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.

Project managementaiai-agentsautomationclaudejirajira-approvaljira-customerjira-jsmjira-queueservice-deskservice-managementsla
Related

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.

grandcamel/JIRA-Assistant-Skills · 51 tokens

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.

grandcamel/JIRA-Assistant-Skills · 47 tokens

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…

grandcamel/JIRA-Assistant-Skills · 121 tokens

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…

grandcamel/JIRA-Assistant-Skills · 119 tokens

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)…

grandcamel/JIRA-Assistant-Skills · 155 tokens

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…

grandcamel/JIRA-Assistant-Skills · 121 tokens