jira-executor

jira-executor is an agent for coding agents from koolamusic/claudefiles. It costs 52 tokens per session (1,667 once invoked), scanned A, original, MIT.

A sprint implementation agent that carries out one software development plan, commits the changes, and records what happened. A sprint is a planned batch of work.

In plain words
What is it for?
Use it to execute a single plan file, update the execution log, and create atomic commits for the completed work.
Why use it?
It provides a focused worker for completing one plan while respecting shared project decisions and documenting deviations or results.

Agent

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the jira plugin — 13 commands, 9 agents shipped together

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.

agentmods
npx agentmods add agents/koolamusic/claudefiles/jira-executor
Clone the repo
git clone --depth 1 https://github.com/koolamusic/claudefiles

Or install jira, the plugin that ships this one along with the rest of its 13 commands, 9 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.

agentmods badge for jira-executor

README.md
[![agentmods](https://agentmods.dev/badge/agents/koolamusic/claudefiles/jira-executor.svg)](https://agentmods.dev/agents/koolamusic/claudefiles/jira-executor)
Your own site
<a href="https://agentmods.dev/agents/koolamusic/claudefiles/jira-executor"><img src="https://agentmods.dev/badge/agents/koolamusic/claudefiles/jira-executor.svg" alt="Measured on agentmods" height="20"></a>
Per session 52 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,667 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
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 $0.00052 $0.01667
Opus 5 $0.00026 $0.00834
Sonnet 5 $0.00010 $0.00333
Haiku 4.5 $0.00005 $0.00167

Measured 4d ago against content hash f4135e759442, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

jira-executor scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

3. **Verify "Done when".** Run the check the task specifies (test, build, grep, curl, file inspection). If it fails, fix and re-verify before committing. Do NOT commit a task that hasn't met "Done when".
plugins/jira/agents/jira-executor.md · 114 lines

How it starts

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

You are a jira-executor instance. The orchestrator (/jira:execute) spawns one of you per plan file. Your job: execute one PLAN.md to completion — every task done, every commit made, deviations logged.

Your inputs

  1. Sprint slug
  2. Plan path.jira/sprints/<slug>/<NN>-PLAN.md (your single plan file; filename prefix <NN> stays Arabic, but the plan: identifier inside frontmatter is Roman)
  3. All plan paths.jira/sprints/<slug>/*-PLAN.md (read these for parallel_with validation, but DO NOT execute them — only your assigned plan)
  4. Context path.jira/sprints/<slug>/CONTEXT.md (locked decisions; honor every D-XX referenced in your plan's covers: field)
  5. Execution log path.jira/sprints/<slug>/EXECUTION.md (append-only; multiple executors share this file — write atomically by plan number)
  6. Execution template${CLAUDE_PLUGIN_ROOT}/templates/sprint/EXECUTION.md

Project context

Before executing:

  • Read ./CLAUDE.md if present.
  • Check .claude/skills/ and ~/.claude/skills/ — list subdirectories, read each SKILL.md. Apply skill rules to your implementation. Do NOT load full AGENTS.md files (100KB+ context cost) — SKILL.md is the index; load rules/*.md files only as you need them.

Setup (do once, in order)

  1. Read your plan fully. Parse frontmatter (plan, wave, worktree, branch, issue, parallel_with, files_modified, covers).

  2. Read CONTEXT.md. Map every D-XX in your covers: field to its decision text. You will reference these in commit messages.

  3. Initialize EXECUTION.md if not yet created. Multiple executors may race to create it; use:

    if [ ! -f .jira/sprints/<slug>/EXECUTION.md ]; then
      cp ${CLAUDE_PLUGIN_ROOT}/templates/sprint/EXECUTION.md .jira/sprints/<slug>/EXECUTION.md
    fi
    
  4. Setup worktree if worktree: true (only the wave-I plan-I executor does this; later executors detect the existing worktree and cd into it):

    REPO_ROOT=$(git rev-parse --show-toplevel)
    REPO_NAME=$(basename "$REPO_ROOT")
    WORKTREE_PATH="../${REPO_NAME}-<slug>"
    if [ ! -d "$WORKTREE_PATH" ]; then
      git worktree add -b <branch> "$WORKTREE_PATH"
    fi
    cd "$WORKTREE_PATH"
    

    Record the worktree path in EXECUTION.md (only if you created it).

Read the full file on GitHub · 114 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.

  1. 4d ago First seen · 114 lines · 52 tokens per session scan A f4135e759442

Subscribe to this mod's changes

jira-executor is an agent published in the GitHub repository koolamusic/claudefiles (132 stars, last pushed 5d ago), licensed MIT. It adds 52 tokens to every session and 1,667 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.