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-evaluatorgit 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-evaluator)<a href="https://agentmods.dev/skills/ngocsangyem/meowkit/jira-evaluator"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/jira-evaluator/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-evaluator"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/jira-evaluator.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.00067 | $0.00412 |
| Opus 5 | $0.00034 | $0.00206 |
| Sonnet 5 | $0.00013 | $0.00082 |
| Haiku 4.5 | $0.00007 | $0.00041 |
Grade A, and why
mk:jira-evaluator 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 8d 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-evaluator
Forks to the jira-evaluator agent. Read-only ticket evaluation.
Triggers
- "evaluate PROJ-123"
- "analyze ticket complexity for KEY"
- "check ticket quality"
Examples
- Single-ticket complexity: "evaluate PROJ-456 — give me Fibonacci range + inconsistencies."
- Pre-estimation: "evaluate PROJ-789 first; I'll estimate after."
See also
- Agent:
../../agents/jira-evaluator.md - Shared:
../jira/references/{install-and-auth,cli-idioms,safety-framework,evaluation-rubric}.md - Peer intelligence:
mk:jira-estimator(point estimate — consumes evaluator output),mk:jira-analyst(full RCA — consumes evaluator complexity signals when present) - Peer execution:
mk:jira-issue(read the ticket),mk:jira-search(historical comparison via JQL),mk:planning-engine(tech review consumes evaluator output)
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.
- 8d ago First seen · 49 lines · 67 tokens per session scan A e6a9886c91c9
mk:jira-evaluator is a skill published in the GitHub repository ngocsangyem/MeowKit (14 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 412 once invoked, about $0.0003 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
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.
plan
Plan features spanning multiple domains: billing (Stripe), auth (RBAC), real-time (Presence), webhooks, jobs (Oban). Use when designing interconnected systems or converting review findings into tasks.
work
Execute Elixir/Phoenix plan tasks with progress tracking. Use after /phx:plan to implement features with mix compile and mix test verification after each step, or --continue to resume interrupted work.
phx-deps-update
Bump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo). Use to upgrade/bump Elixir dependencies or when versions fall behind. NOT for deps.get failures (phx-investigate).
rfi-management
Complete RFI (Request for Information) management system. Create, track, route, and analyze RFIs with automatic notifications and response deadline tracking.
daily-report-generator
Automatically generate daily construction reports from field data, worker inputs, weather, and progress photos. Creates professional PDF reports.