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 agentmods add agents/koolamusic/claudefiles/jira-executorgit clone --depth 1 https://github.com/koolamusic/claudefilesWrote 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/agents/koolamusic/claudefiles/jira-executor)<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>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 | $0.00052 | $0.01667 |
| Opus 5 | $0.00026 | $0.00834 |
| Sonnet 5 | $0.00010 | $0.00333 |
| Haiku 4.5 | $0.00005 | $0.00167 |
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". 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
- Sprint slug
- Plan path —
.jira/sprints/<slug>/<NN>-PLAN.md(your single plan file; filename prefix<NN>stays Arabic, but theplan:identifier inside frontmatter is Roman) - All plan paths —
.jira/sprints/<slug>/*-PLAN.md(read these forparallel_withvalidation, but DO NOT execute them — only your assigned plan) - Context path —
.jira/sprints/<slug>/CONTEXT.md(locked decisions; honor every D-XX referenced in your plan'scovers:field) - Execution log path —
.jira/sprints/<slug>/EXECUTION.md(append-only; multiple executors share this file — write atomically by plan number) - Execution template —
${CLAUDE_PLUGIN_ROOT}/templates/sprint/EXECUTION.md
Project context
Before executing:
- Read
./CLAUDE.mdif present. - Check
.claude/skills/and~/.claude/skills/— list subdirectories, read eachSKILL.md. Apply skill rules to your implementation. Do NOT load fullAGENTS.mdfiles (100KB+ context cost) —SKILL.mdis the index; loadrules/*.mdfiles only as you need them.
Setup (do once, in order)
-
Read your plan fully. Parse frontmatter (
plan,wave,worktree,branch,issue,parallel_with,files_modified,covers). -
Read CONTEXT.md. Map every
D-XXin yourcovers:field to its decision text. You will reference these in commit messages. -
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 -
Setup worktree if
worktree: true(only the wave-I plan-I executor does this; later executors detect the existing worktree andcdinto 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).
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 · 114 lines · 52 tokens per session scan A f4135e759442
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.
Other agents, from other repositories
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
Orchestrator
Task coordination and agent delegation.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
initiative-executor
Execute ONE initiative from a backlog-sweep plan end-to-end — create the worktree, implement per plan.md, validate, open the PR, return a >> envelope. Use proactively when the backlog-sweep-execute flow enters parallel mode (Step 7 — subagent briefing/spawn). Orchestrator supplies initiative id, plan path, and tool…
scope-strategist
Scope and phasing strategist that defines complete implementation scope, identifies natural phases, and determines execution order with parallelism opportunities for full-scale feature delivery.
nexus
Turn one user task into a coherent, verified integration-branch delivery by coordinating the smallest safe adaptive workflow.