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-devgit 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-dev)<a href="https://agentmods.dev/skills/ngocsangyem/meowkit/jira-dev"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/jira-dev.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.00086 | $0.00612 |
| Opus 5 | $0.00043 | $0.00306 |
| Sonnet 5 | $0.00017 | $0.00122 |
| Haiku 4.5 | $0.00009 | $0.00061 |
Grade A, and why
mk:jira-dev 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 4d 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-dev
Forks to the jira-dev agent. Pure artifact generation — the user reviews and runs the resulting git/gh commands.
Triggers
- "branch name for PROJ-123"
- "PR description for PROJ-123"
- "parse commits in main..HEAD for issue keys"
- "link this commit to PROJ-123"
- "link this PR to PROJ-123"
Examples
- Branch: "give me a branch name for PROJ-123"
- PR: "draft a PR title and body from PROJ-123"
- Smart-commit: "generate a 'Closes PROJ-123' footer for my last 5 commits"
Handoff
mk:ship may invoke bash $CLAUDE_PROJECT_DIR/.claude/skills/jira/scripts/jira-as.sh dev branch-name <KEY> during its branch-creation step (documentation-only — no automatic wiring exists today). Users opt in by passing the Jira key context to mk:ship.
See also
- Agent:
../../agents/jira-dev.md - Shared:
../jira/references/{install-and-auth,cli-idioms,safety-framework}.md - Domain refs:
references/branch-naming.md— convention reference (<type>/<KEY>-<slug>)references/smart-commits.md— smart-commit syntax for closing/transitioning from commit messagesreferences/commit-messages.md— Atlassian-aware commit-message conventions
- Peer leaves:
mk:ship(consumesdev branch-name+dev pr-description),mk:jira-issue(issue must exist before branch creation),mk:jira-lifecycle(transitions via smart-commit footer)
Gotchas
- (none yet)
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 60 lines · 86 tokens per session scan A c3a4c90bcead
mk:jira-dev is a skill published in the GitHub repository ngocsangyem/MeowKit (14 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 612 once invoked, about $0.0004 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.
pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
phx-pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
split-and-ship
Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".
magpie-setup-override-upstream
Walk an adopter through promoting a local .apache-magpie-overrides/ .md file into a PR against apache/magpie. After the PR merges and the adopter runs /magpie-setup upgrade, the override file is no longer needed and the skill prompts for its removal.
magpie-setup-shared-config-sync
Commit + push the user's shared Claude config to the /.claude-config private dotfile-style sync repo. Inspects for uncommitted local edits and unpushed commits, drafts a commit message, and after explicit approval commits and pushes. Runs git pull --rebase first if the local checkout is behind, so a push never…