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-analystgit 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-analyst)<a href="https://agentmods.dev/skills/ngocsangyem/meowkit/jira-analyst"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/jira-analyst/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-analyst"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/jira-analyst.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.00093 | $0.00542 |
| Opus 5 | $0.00046 | $0.00271 |
| Sonnet 5 | $0.00019 | $0.00108 |
| Haiku 4.5 | $0.00009 | $0.00054 |
Grade A, and why
mk:jira-analyst 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 6d 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-analyst
Forks to the jira-analyst agent. Read-only. The agent has Write tool privilege ONLY for persisting the report to tasks/reports/jira-analyze-*.md — it never writes to Jira itself.
Triggers
- "analyze PROJ-123"
- "rca for PROJ-123"
- "describe PROJ-123 including the screenshots"
Examples
- Standalone: "analyze PROJ-456 — what is this ticket about?"
- With investigation: "I investigated and found ; now analyze PROJ-456 with full RCA"
- Media-heavy: "PROJ-789 has 3 screenshots — analyze them and synthesize"
See also
- Agent:
../../agents/jira-analyst.md - Shared:
../jira/references/{install-and-auth,cli-idioms,safety-framework}.md - Peer intelligence:
mk:jira-evaluator(complexity signals),mk:jira-estimator(point estimate) - Peer execution:
mk:jira-issue(read ticket fields incl. attachments),mk:jira-collaborate(post analysis as comment — seemk:jira-collaborate/references/comment-templates.md) - Output: report at
tasks/reports/jira-analyze-*.mdconsumable bymk:planning-engineand downstream skills.
Gotchas
- (none yet)
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.
- 6d ago First seen · 52 lines · 93 tokens per session scan A 2e03f6750a72
mk:jira-analyst is a skill published in the GitHub repository ngocsangyem/MeowKit (14 stars, last pushed 1mo ago), licensed MIT. It adds 93 tokens to every session and 542 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
clash-resolution-analyzer
Analyze BIM clash detection results and suggest resolutions. Prioritize clashes, identify patterns, assign responsibility, and track resolution status.
bug-triage
Investigate a Jira bug from its key to a root-cause verdict — classify bug-vs-feature, fan out read-only Explore agents across the repo, adversarially confirm the cause, and write a tasks/ -triage.md artifact a lean fix-planner can pick up. Orchestration only; read-only, never touches Jira, stops at verdict +…
customer-escalation
Package an escalation for engineering, product, or leadership with full context. Use when a bug needs engineering attention beyond normal support, multiple customers report the same issue, a customer is threatening to churn, or an issue has sat unresolved past its SLA.
skill-incident-management
Incident response, postmortem facilitation, root cause analysis (RCA), blameless culture, incident timeline documentation, and incident classification. Use when responding to production incidents, writing incident reports, facilitating postmortems, or improving incident response processes.
triage
Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.