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.
git 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/agents/ngocsangyem/meowkit/jira-jsm)<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.
<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>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.5 | $0.00034 | $0.00310 |
| Sonnet 5.5 | $0.00017 | $0.00155 |
| Haiku 4.5 | $0.00009 | $0.00078 |
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 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.
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) orpublic(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`
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 · 77 lines · 86 tokens per session scan A 662f4fe4e92e
jira-jsm is an agent published in the GitHub repository ngocsangyem/MeowKit (15 stars, last pushed 3mo ago), licensed MIT. It adds 86 tokens to every session and 776 once invoked, about $0.0003 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-08-30.
Other agents, from other repositories
sales-closer
PEITHO, fechamento da squad Sales. Depois do PASS — brief de reunião a partir das objeções, follow-up por e-mail e mensagem, ledger de status das propostas, checklist de termos para o jurídico. Só envia com PASS do QA e confirmação; nunca altera preço. Use para apresentação ao cliente e pós-envio.
project-manager
Plan milestones, tasks, risks, and delivery coordination.
pm
Product manager. Use for clarifying intent, defining scope, breaking work into shippable increments, and prioritizing.
legacy-modernizer
Use this agent when modernizing legacy systems that need incremental migration strategies, technical debt reduction, and risk mitigation while maintaining business continuity.
pm-mean
MEAN stack Product Manager. Writes PRDs with features, acceptance criteria, and priorities. Also performs final acceptance review. Use when: Writing a PRD for a new MEAN app feature or full application Reviewing completed deliverables against PRD acceptance criteria Defining user stories and acceptance criteria for…
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.