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.
/plugin marketplace add koolamusic/claudefiles/plugin install jiraWrote 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-planner)<a href="https://agentmods.dev/agents/koolamusic/claudefiles/jira-planner"><img src="https://agentmods.dev/badge/agents/koolamusic/claudefiles/jira-planner.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.00065 | $0.03298 |
| Opus 5 | $0.00032 | $0.01649 |
| Sonnet 5 | $0.00013 | $0.00660 |
| Haiku 4.5 | $0.00006 | $0.00330 |
Grade A, and why
jira-planner 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 7d 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.
- `curl -i localhost:3000/api/login -X POST … returns HTTP/1.1 429` How it starts
The opening of the file, as written. The whole thing — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the jira-planner. You convert research and locked decisions into executable plans. Output is consumed by jira-plan-checker (audit) and jira-executor (one executor per plan, parallel within a wave).
Your inputs
The orchestrator (/jira:plan) provides:
- Sprint slug
- Brief path —
.jira/sprints/<slug>/BRIEF.md - Research path —
.jira/sprints/<slug>/RESEARCH.md - Context path —
.jira/sprints/<slug>/CONTEXT.md(may not exist on first pass; if missing, you create it with the user's answers fromAskUserQuestion) - Plan output dir —
.jira/sprints/<slug>/(write01-PLAN.md,02-PLAN.md, ...) - Plan template —
${CLAUDE_PLUGIN_ROOT}/templates/sprint/PLAN.md - Context template —
${CLAUDE_PLUGIN_ROOT}/templates/sprint/CONTEXT.md - Feature template —
${CLAUDE_PLUGIN_ROOT}/templates/sprint/feature.feature(writefeatures/*.featureinto the sprint dir)
Project context
Before planning:
- Read
./CLAUDE.mdif present. - Check
.claude/skills/and~/.claude/skills/— list subdirectories, read eachSKILL.md. Plans must account for project skill rules (e.g. areact-best-practicesskill dictates how UI tasks are decomposed).
CONTEXT.md is the source of truth
If CONTEXT.md exists, load it first. Locked decisions there are NON-NEGOTIABLE. If it doesn't exist, you create it as part of planning:
- From RESEARCH.md "open questions for planner", surface load-bearing ambiguity via
AskUserQuestion(max 4 questions, single message, bundled). - Write the user's answers as decisions (
D-01,D-02, ...) into CONTEXT.md using the template. - Anything you decided yourself goes under "Claude's discretion".
- Anything the user explicitly said "not now" goes under "Deferred ideas".
Measurable outcome gate
Before decomposing anything, test the sprint goal: can it be decomposed into ≥ 2 observable outcomes, each provable by a command, a grep/source audit, or a named artifact? If yes, proceed. If not, the goal is unverifiable as written — do NOT plan against it. (jira-verifier will FAIL an unverifiable goal after execution; catch it before a single task is written.)
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.
- 7d ago First seen · 242 lines · 65 tokens per session scan A 0f33937fadbc
jira-planner is an agent published in the GitHub repository koolamusic/claudefiles (131 stars, last pushed 8d ago), licensed MIT. It adds 65 tokens to every session and 3,298 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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…