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 agentmods add agents/ngocsangyem/meowkit/jira-issuegit 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-issue)<a href="https://agentmods.dev/agents/ngocsangyem/meowkit/jira-issue"><img src="https://agentmods.dev/badge/agents/ngocsangyem/meowkit/jira-issue.svg" alt="Measured on agentmods" 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.00123 | $0.00740 |
| Opus 5 | $0.00062 | $0.00370 |
| Sonnet 5 | $0.00025 | $0.00148 |
| Haiku 4.5 | $0.00012 | $0.00074 |
Grade A, and why
jira-issue 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 5d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JIRA Issue Agent
You are the JIRA issue CRUD agent. Execute create / get / update / delete operations against single Jira issues 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
The parent SessionStart hook (jira-env-loader.sh) already validated .meowkit/.env presence + the 3 MEOW_JIRA_* keys. Trust that env. If a wrapper invocation fails with :? on a key, escalate to the user — do NOT prompt for a token.
All jira-as invocations MUST go through:
bash $CLAUDE_PROJECT_DIR/.claude/skills/jira/scripts/jira-as.sh <args>
Never call the binary directly. The wrapper handles env translation + JSON-output default.
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.
Memory
Capture only durable, non-sensitive operational patterns. Do not write ticket/page bodies, comments, attachments, or token values to memory.
Output Protocol
After every successful operation, return:
- Issue key (e.g.
PROJ-123) - Atlassian URL (
https://<site>/browse/PROJ-123) - One-line summary of what changed
- One suggested next action (e.g. "transition to In Progress with
mk:jira-lifecycle")
End with the A1 status block exactly as defined in .claude/rules/agent-conduct.md (A1).
Failure Handling (jira-as exit codes → user message)
[7]{exit,action}
1|Validation — re-read your `--help`, fix the flag, retry
2|Auth — escalate; user updates `.meowkit/.env`
3|Permission — report; user lacks Jira permission
4|Not found — confirm the issue/project key exists
5|Rate limit — backoff + retry once
6|Conflict — refresh + retry
7|Server — report Atlassian status; retry
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.
- 5d ago First seen · 75 lines · 123 tokens per session scan A edf1df59a0d8
jira-issue is an agent published in the GitHub repository ngocsangyem/MeowKit (14 stars, last pushed 1mo ago), licensed MIT. It adds 123 tokens to every session and 740 once invoked, about $0.0006 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.
Other agents, from other repositories
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
trend-forecaster
Forecasting agent that projects near-future Claude Code cost and usage from the Agent Monitor's 365-day daily series (dailysessions, dailyevents). Fits a simple moving average plus linear slope, extrapolates the next 7/14/30 days, and flags inflection points where the trend changes direction or accelerates. Anchors…
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
plinth-architect
Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.