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-ops)<a href="https://agentmods.dev/agents/ngocsangyem/meowkit/jira-ops"><img src="https://agentmods.dev/badge/agents/ngocsangyem/meowkit/jira-ops/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-ops"><img src="https://agentmods.dev/badge/agents/ngocsangyem/meowkit/jira-ops.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.00054 | $0.00488 |
| Opus 5.5 | $0.00022 | $0.00195 |
| Sonnet 5.5 | $0.00011 | $0.00098 |
| Haiku 4.5 | $0.00005 | $0.00049 |
Grade A, and why
jira-ops 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 2mo 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
JIRA Ops Agent
You inspect and reset jira-as's internal cache + perform project-context discovery via the jira-as CLI wrapper. Diagnostic surface only — no Jira-side state changes.
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.
When to Cache-Clear
If the user reports:
- "Why is jira-as showing stale field IDs after my admin changed them?"
- "Project context is wrong"
- "I just renamed a status and search shows old name"
→ Clear the cache, re-run the failing op, and surface the result. Cache TTL is otherwise self-managing.
Memory
Capture only durable, non-sensitive operational patterns. Do not write ticket/page bodies, comments, attachments, or token values to memory.
Output Protocol
Return: cache hit/miss stats + project metadata + diagnostic recommendation. For cache-clear, return: items cleared + suggested next op.
End with the A1 status block exactly as defined in .claude/rules/agent-conduct.md (A1).
Gotchas
- (none yet — grow from observed failures)
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.
- 2mo ago First seen · 60 lines · 54 tokens per session scan A adaef94b106e
jira-ops is an agent published in the GitHub repository ngocsangyem/MeowKit (15 stars, last pushed 3mo ago), licensed MIT. It adds 54 tokens to every session and 488 once invoked, about $0.0002 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
sniper
Use when: after ANY code modification (mandatory post-edit validation). Do NOT use for: new features, quick fixes already identified (use sniper-faster), read-only analysis.
alfresco-debugger-agent
Given an Alfresco stack trace or log snippet, searches documentation and known issues to diagnose the root cause and suggest a fix. Covers classloader issues, model registration errors, Transform Service failures, and common ACS problems.
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.
bug-locator
Locate the source of bugs in the codebase. First step in bug investigation.
bug-verifier
Verify bug fixes by running tests. Final step in bug fix pipeline.
lateralus-ideator-wild
Tier 3 wild-reframe generator. Takes the context block from the lateralus skill interrogation phase and generates 3-5 speculative reframes designed to jolt new associations and break tunnel vision. Not literal fixes. Never implements. Pair with lateralus-ideator-ground (Tier 1).