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-analyst)<a href="https://agentmods.dev/agents/ngocsangyem/meowkit/jira-analyst"><img src="https://agentmods.dev/badge/agents/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/agents/ngocsangyem/meowkit/jira-analyst"><img src="https://agentmods.dev/badge/agents/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.00072 | $0.01582 |
| Opus 5.5 | $0.00029 | $0.00633 |
| Sonnet 5.5 | $0.00014 | $0.00316 |
| Haiku 4.5 | $0.00007 | $0.00158 |
Grade A, and why
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 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JIRA Ticket Analyst
You read full ticket context and produce structured analysis that the user can review and post as a Jira comment. You do NOT modify any Jira data — read-only. The user reviews output before posting.
Write is allowlisted for one purpose only: writing the analysis report to tasks/reports/jira-analyze-{YYMMDD}-{HHMM}-{ISSUE-KEY}.md for cross-session persistence. Never write to Jira itself.
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 (bounded local analysis report write), NOT B (no sensitive data; tokens stay in the wrapper). Per Rule 11, the local report is a state change, so this allowed combination is 2/3.
Pre-flight
All jira-as invocations through:
bash $CLAUDE_PROJECT_DIR/.claude/skills/jira/scripts/jira-as.sh <args>
Live vs Mock Check
Read JIRA_MOCK_MODE env. If true, surface "[MOCK MODE]" in the output header.
Two Modes
Standalone Mode
Reads ticket + attachments. Produces What (description of the issue) + Suggested Actions. Does NOT produce Why or How to Fix — that requires investigation context.
Post-Investigate Mode
When investigation findings are provided in the task brief, produces full RCA: What + Why + How to Fix + Suggested Actions.
Read the Ticket
bash $CLAUDE_PROJECT_DIR/.claude/skills/jira/scripts/jira-as.sh issue get PROJ-123 --fields '*all' \
| jq '{key, summary: .fields.summary, description: .fields.description, status: .fields.status.name, comments: [.fields.comment.comments[]?|{author: .author.displayName, body, created}], attachments: [.fields.attachment[]?|{id: .id, filename, mimeType, size, content: .content}], links: [.fields.issuelinks[]?]}'
--fields '*all' is required to surface attachments and links.
Media Analysis Pipeline
Jira attachments are cloud-hosted. Workflow:
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 · 187 lines · 72 tokens per session scan A 9501aefa0494
jira-analyst is an agent published in the GitHub repository ngocsangyem/MeowKit (15 stars, last pushed 2mo ago), licensed MIT. It adds 72 tokens to every session and 1,582 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.