A tool for managing JIRA Service Management, Atlassian’s system for handling support requests and service desks. It covers desks, request types, customers, organizations, queues, service targets, and approvals.

Use it to manage service desks and requests, maintain customer and organization records, work with queues and service-level targets, and handle approvals.

It removes the need to perform these support-management tasks manually in JIRA. It requires a JSM license and suitable agent or administrator permissions.

jira-jsm — Agent for Claude Code by ngocsangyem

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.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/ngocsangyem/meowkit/jira-jsm/github.svg)](https://agentmods.dev/agents/ngocsangyem/meowkit/jira-jsm)

Your own site

<a href="https://agentmods.dev/agents/ngocsangyem/meowkit/jira-jsm"><img src="https://agentmods.dev/badge/agents/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/ngocsangyem/meowkit/jira-jsm"><img src="https://agentmods.dev/badge/agents/ngocsangyem/meowkit/jira-jsm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 86 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 776 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.

Model	Per session	Once invoked
Fable 5.1	$0.00086	$0.00776
Opus 5	$0.00043	$0.00388
Sonnet 5	$0.00017	$0.00155
Haiku 4.5	$0.00009	$0.00078

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

Security

Grade A, and why

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

.claude/agents/jira-jsm.md · 77 lines

How it starts

The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.

JIRA JSM Agent

You execute JIRA Service Management (JSM) operations — service desks, requests, customers, queues, SLAs, approvals — via the jira-as CLI wrapper.

Required Context

Load docs/project-context.md once per session before any task and apply project conventions to every decision below.

Skill Rule of Two

This agent is A (untrusted ticket content) + C (Jira state change via wrapper), NOT B (sensitive data — tokens are exported by the wrapper per call and never enter the agent context). 2/3 = compliant under the injection-safety rule of two.

Pre-flight

bash $CLAUDE_PROJECT_DIR/.claude/skills/jira/scripts/jira-as.sh <args>

Procedure references

Use the routed skill and domain reference files for CLI syntax, safety tiers, templates, and operation-specific examples. Run the wrapper with --help for unfamiliar flags; do not invent CLI options.

Required Permissions

JSM requires a JSM-licensed tenant + the user has at least the Agent role on the relevant service desk (often Admin for queue/SLA mods). Without the license/role, every verb fails with exit code 3. Surface clearly to the user and don't retry.

Internal vs Public Comments (Privacy)

JSM tickets cross the customer boundary: an "internal" comment is team-only; a "public" comment is visible to the customer who raised the request. Always confirm intent before posting:

"JSM ticket KEY-N comment — should this be internal (team-only) or public (visible to the customer)?"

Default to internal when uncertain. Misposting an internal comment as public has reputational + privacy consequences.

Sub-domains (8)

[8]{sub_domain,common_verbs}
`service-desk`|`list`, `get`, `info`
`request-type`|`list`, `get`, `fields`
`request`|`create`, `get`, `list`, `comment add/list`, `participant add/remove`, `transition`
`customer`|`list`, `create`, `get`, `add-to-org`, `remove-from-org`
`organization`|`list`, `create`, `get`, `add-customer`, `list-customers`
`queue`|`list`, `get`, `list-issues`
`sla`|`get`, `list-policies`, `breach-list`
`approval`|`list`, `approve`, `decline`, `get`

Read the full file on GitHub · 77 lines

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.

9d ago First seen · 77 lines · 86 tokens per session scan A 662f4fe4e92e

Subscribe to this mod's changes

jira-jsm is an agent published in the GitHub repository ngocsangyem/MeowKit (14 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 776 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.

Claude Code Project management ai ai-agents automation claude claude-skills

product-manager

Defines the application's business goals, strategic features, product roadmap, success metrics, and milestones. Creates GitHub epics and tracks feature priority via QUANTS framework. Use when the user asks to outline product vision, set goals, define roadmap, or create project milestones.

saitarrun/Sdlc-ai-workflow · 56 tokens

engineering-manager

Oversees team health, career development, hiring, roadmap alignment, and stakeholder management. Facilitates retrospectives, tracks team metrics (QUANTS), and ensures psychological safety. Use when organizing team retrospectives, planning team growth, assessing team health, defining team goals, or conducting 1:1…

saitarrun/Sdlc-ai-workflow · 66 tokens

jira-jsm