A command for running approved Jira work plans and preparing new Jira tickets. Jira is a tool teams use to track tasks, bugs, and other project work.

Use it to execute approved plans, create batches of proposed tickets for later approval, and coordinate Jira and Bitbucket work from a repository.

It separates execution from approval so plans are not run until a person has marked them approved, while keeping the work recorded in files.

jira-run — Command for Claude Code by mumerfarooq-con/asdlc-tools

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add mumerfarooq-con/asdlc-tools

Claude Code

/plugin install asdlc

Made for: Claude Code.

Or install asdlc, the plugin that ships this one along with the rest of its 5 commands, 15 agents.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/mumerfarooq-con/asdlc-tools/jira-run/github.svg)](https://agentmods.dev/commands/mumerfarooq-con/asdlc-tools/jira-run)

Your own site

<a href="https://agentmods.dev/commands/mumerfarooq-con/asdlc-tools/jira-run"><img src="https://agentmods.dev/badge/commands/mumerfarooq-con/asdlc-tools/jira-run/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/mumerfarooq-con/asdlc-tools/jira-run"><img src="https://agentmods.dev/badge/commands/mumerfarooq-con/asdlc-tools/jira-run.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,333 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.

Model	Per session	Once invoked
Fable 5.1	$0.00017	$0.02333
Opus 5.5	$0.00007	$0.00933
Sonnet 5.5	$0.00003	$0.00467
Haiku 4.5	$0.00002	$0.00233

Measured 4d ago against content hash 9c8ff7e49e98, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

jira-run 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.

plugins/asdlc/commands/jira-run.md · 107 lines

How it starts

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

/asdlc:jira-run

One run does two phases: first it EXECUTES plans I've already approved, then it PLANS new tickets and leaves them for me to approve. Approval is never something you do — it only ever comes from me setting status: approved in a plan file.

Scripts live in ${CLAUDE_PLUGIN_ROOT}/jira/scripts/. Always call them by that full path, as written below; run them from the repo root. They read the project's .asdlc/jira.conf and the token env vars.

0. Config, lock, args

Read the config: ${CLAUDE_PLUGIN_ROOT}/jira/scripts/jira-conf.sh. If it fails (no config), tell me to run /asdlc:jira-setup and STOP. Note TARGET_BRANCH — every <TARGET_BRANCH> below is that value.
Take the run lock: ${CLAUDE_PLUGIN_ROOT}/jira/scripts/run-state.sh lock. It prints a run id: keep it as <RUN_ID>.
- Exit 10 means another run holds the lock. Show me the holder it names (who, since when) and STOP. If I tell you that run crashed, I clear it myself, or I tell you to run ${CLAUDE_PLUGIN_ROOT}/jira/scripts/run-state.sh force-unlock — never run that on your own.
- Always release the lock before you finish, including on error: ${CLAUDE_PLUGIN_ROOT}/jira/scripts/run-state.sh unlock <RUN_ID>.
Read the phase flags from the arguments: --plan-only (Phase B only), --execute-only (Phase A only), --reset-executing (before Phase A, run ${CLAUDE_PLUGIN_ROOT}/jira/scripts/run-state.sh reset-executing: every plan a crashed run left executing goes back to approved, if its approved part is unchanged — what the run logged under the plan's Progress section doesn't count. Relay what it prints; a plan it refuses needs a re-stamp and my re-approval). Everything else is a selection to hand to jira-mine in Phase B.

Phase A — execute approved plans (skip if --plan-only)

List plan files: ls ./plans/*.plan.md. For each, run ${CLAUDE_PLUGIN_ROOT}/scripts/plan-state.sh check <plan> and act on the word it prints:

RUNNABLE → implement it (steps below).
STALE → skip; report ": plan changed since approval — re-approve".
EXECUTING PENDING DONE FAILED SKIP MISSING → skip (mention EXECUTING/FAILED, stay quiet on the rest).

Read the full file on GitHub · 107 lines

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.

4d ago Changed · +14 lines 9c8ff7e49e98
9d ago First seen · 93 lines · 17 tokens per session scan A 8e1d55055e3c

Subscribe to this mod's changes

jira-run is a command published in the GitHub repository mumerfarooq-con/asdlc-tools (2 stars, last pushed 5d ago), licensed MIT. It adds 17 tokens to every session and 2,333 once invoked, about $0.0001 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-10-09.

Claude Code Code review Multi-Agent Project management ai-agents claude-code-plugin sdlc

poc

Before building on an unproven idea, get a timeboxed yes/no answer — start a hypothesis-driven POC that skips 80% of the production pipeline and forces ship/pivot/kill at expiry, then promote a shipped POC through the audits it skipped.

avelikiy/great_cto · 54 tokens

spec

Know the problem but not yet the product, the requirements or the design? Run it — you get, stage by stage, a discovery plan (/spec discover), a PRD (/spec prd) and a build spec: requirements.md + design.md + tasks.md (/spec or /spec build). Run before writing any code.

avelikiy/great_cto · 71 tokens

jira-run