agentmods.dev

mk:jira-lifecycle

mk:jira-lifecycle is a skill for Claude Code from ngocsangyem/MeowKit. It costs 86 tokens per session (846 once invoked), scanned A, original, MIT.

A tool for moving Jira issues through their workflow and managing assignments, resolutions, versions, and components.

In plain words
What is it for?
Transition issues between statuses, assign or reopen them, resolve them, and manage project versions and components.
Why use it?
It helps keep an issue's status and ownership aligned with the project's actual workflow.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: agent in frontmatter.

not rated 14repo 1mo ago A scan 86 tokens original MIT

Good fit Transition issues between statuses, assign or reopen them, resolve them, and manage project versions and components.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ngocsangyem/meowkit/jira-lifecycle
View source ↗ ngocsangyem/MeowKit docs.meowkit.dev
Install

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.

Any agent
npx skills add ngocsangyem/MeowKit --skill jira-lifecycle
Clone the repo
git clone --depth 1 https://github.com/ngocsangyem/MeowKit

Made for: Claude Code.

Wrote 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.

agentmods badge for mk:jira-lifecycle

README.md
[![agentmods](https://agentmods.dev/badge/skills/ngocsangyem/meowkit/jira-lifecycle/github.svg)](https://agentmods.dev/skills/ngocsangyem/meowkit/jira-lifecycle)
Your own site
<a href="https://agentmods.dev/skills/ngocsangyem/meowkit/jira-lifecycle"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/jira-lifecycle/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.

agentmods 80×15 button for mk:jira-lifecycle

Your own site · 80×15
<a href="https://agentmods.dev/skills/ngocsangyem/meowkit/jira-lifecycle"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/jira-lifecycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 86 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 846 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00086 $0.00846
Opus 5 $0.00043 $0.00423
Sonnet 5 $0.00017 $0.00169
Haiku 4.5 $0.00009 $0.00085

Measured 8d ago against content hash fb997c8c8a32, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

mk:jira-lifecycle 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.

.claude/skills/jira-lifecycle/SKILL.md · 67 lines

How it starts

The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.

mk:jira-lifecycle

Forks to the jira-lifecycle agent. lifecycle transition takes the issue key positional + a --to "Status Name" flag (or --id <transition_id>).

Workflow discovery is mandatory before suggesting transitions. The agent reads tasks/jira-workflows/ (instance-discovered cache) and runs bash $CLAUDE_PROJECT_DIR/.claude/skills/jira/scripts/fetch-workflow.sh <KEY> if absent. See references/workflow-discovery.md. The references/patterns/*.md files are illustrative concepts only — they are NOT your project's actual workflow.

Triggers

  • "transition PROJ-123 to In Progress"
  • "mark PROJ-123 as Done with resolution Fixed"
  • "assign PROJ-123 to john.doe"
  • "reopen PROJ-123"
  • "release version v1.0.0 in PROJ"

Examples

  • Status change: "move PROJ-123 to In Review with comment 'ready for QA'"
  • Resolution-required: "close PROJ-456 with resolution Won't Fix"
  • Assignment: "assign all my open PROJ tickets to john.doe" (the agent will refuse — that's bulk; redirect to mk:jira-bulk)

See also

  • Agent: ../../agents/jira-lifecycle.md
  • Shared: ../jira/references/{install-and-auth,cli-idioms,safety-framework}.md
  • Authoritative source for THIS project's workflow (discovered, not templated):
    • references/workflow-discovery.md — discovery + caching protocol (READ FIRST)
    • tasks/jira-workflows/<workflow-slug>.md — discovered workflow definitions
    • tasks/jira-workflows/_schemes/<PROJECT_KEY>.md — project → workflow mapping
    • Discovery script: bash $CLAUDE_PROJECT_DIR/.claude/skills/jira/scripts/jira-as.sh ... — wrapped by fetch-workflow.sh
  • Domain refs:
    • references/workflow-transitions.md — common transition idioms + resolution-required patterns
  • Educational concept patterns (illustrative shapes, NOT authoritative for your instance — always prefer the discovered cache above):
    • references/patterns/standard-workflow.md — basic 3-state lifecycle (concept)
    • references/patterns/software-dev-workflow.md — engineering-team flow (concept)
    • references/patterns/jsm-request-workflow.md — JSM ITIL flow (concept)
    • references/patterns/incident-workflow.md — incident handling (concept)
  • Peer leaves: mk:jira-bulk (bulk transition; reads same workflow cache), mk:jira-jsm (JSM-specific transitions), mk:jira-collaborate (transition --comment body templates)

Read the full file on GitHub · 67 lines

Files

What ships with it

10 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.

Changes

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.

  1. 8d ago First seen · 67 lines · 86 tokens per session scan A fb997c8c8a32

Subscribe to this mod's changes

mk:jira-lifecycle 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 846 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.

Claude CodeProject managementaiai-agentsautomationclaudejirajira-assignjira-componentjira-lifecyclejira-resolvejira-transitionjira-version
Related

Other skills, from other repositories

jira-administration

Complete JIRA project and system administration including projects, automation rules, permissions, users, notifications, screens, issue types, and workflows. Use when managing project structure, automating work, configuring team access, or setting up issue tracking.

grandcamel/JIRA-Assistant-Skills · 51 tokens

jira-service-management

Complete ITSM/ITIL workflow support for JSM - service desks, requests, SLAs, customers, approvals, knowledge base. Use when managing service desk requests, tracking SLAs, or handling customer operations.

grandcamel/JIRA-Assistant-Skills · 47 tokens

jira-time-tracking

Time tracking, worklogs, and time reports. TRIGGERS: 'log time', 'time spent on', 'log hours', 'log work', 'worklog', 'time tracking', 'timesheet', 'how much time', 'time logged', 'time report', 'export timesheet', 'set estimate', 'remaining estimate', 'original estimate'. Use for time-related queries and operations…

grandcamel/JIRA-Assistant-Skills · 121 tokens

jira-custom-fields

Custom field discovery and configuration. TRIGGERS: 'field ID for', 'what's the field ID', 'what is the field ID', 'list custom fields', 'what fields are available', 'what custom fields', 'show custom fields', 'customfield', 'find field', 'agile fields', 'configure agile fields', 'story points field'. Use for JIRA…

grandcamel/JIRA-Assistant-Skills · 119 tokens

jira-issue-management

Core JIRA issue CRUD - create bugs/tasks/stories, get issue details, update fields, delete issues. TRIGGERS: 'show me [KEY]', 'get issue [KEY]', 'view issue', 'create a bug/task/story', 'update [KEY]', 'delete [KEY]', 'details of [KEY]', 'look up [KEY]', 'what's in [KEY]'. NOT FOR: epics (use jira-agile)…

grandcamel/JIRA-Assistant-Skills · 155 tokens

jira-issue-relationships

Issue linking, blockers, and dependency analysis. TRIGGERS: 'what's blocking', 'what is blocking', 'is blocked by', 'link issues', 'link to', 'blockers for', 'depends on', 'clone issue', 'clone with', 'blocking chain', 'dependency graph', 'show dependencies', 'get blockers', 'relates to', 'duplicates'. Use for issue…

grandcamel/JIRA-Assistant-Skills · 121 tokens