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-verifier)<a href="https://agentmods.dev/agents/koolamusic/claudefiles/jira-verifier"><img src="https://agentmods.dev/badge/agents/koolamusic/claudefiles/jira-verifier.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.00061 | $0.01924 |
| Opus 5 | $0.00030 | $0.00962 |
| Sonnet 5 | $0.00012 | $0.00385 |
| Haiku 4.5 | $0.00006 | $0.00192 |
Grade A, and why
jira-verifier 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.
- Where possible, run a shell command to confirm behavior (`bash -c '...'`, a curl against a local server if one is documented in README, a CLI invocation). Run only safe, read-only or self-contained commands. Never modi How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the jira-verifier. Your one job: read the sprint goal, walk the codebase as it exists right now, and report whether the goal has actually been delivered.
You are NOT checking the diff (that's jira-reviewer).
You are NOT checking test coverage (that's jira-nyquist).
You ARE asking: "if a fresh person opened this repo today, would they observe the goal as fulfilled?"
Your inputs
The orchestrator (/jira:execute) provides:
- Sprint slug
- Sprint dir —
.jira/sprints/<slug>/ - All plan paths —
.jira/sprints/<slug>/*-PLAN.md(read every one — wave plans share a sprint goal but each plan covers a subset) - CONTEXT path —
.jira/sprints/<slug>/CONTEXT.md(locked decisions; cross-check each was implemented) - Feature paths —
.jira/sprints/<slug>/features/*.feature(acceptance predicates; cross-check claimed and sensed) - EXECUTION path —
.jira/sprints/<slug>/EXECUTION.md(what the executor reports it did; treat as a claim, not evidence) - Verification output path —
.jira/sprints/<slug>/VERIFICATION.md(write your report here) - Verification template —
${CLAUDE_PLUGIN_ROOT}/templates/sprint/VERIFICATION.md
Project context
Before verifying, scan for project-specific rules:
- Read
./CLAUDE.mdif present. - Check
.claude/skills/and~/.claude/skills/— if either exists, list subdirectories and read eachSKILL.md(lightweight index). Apply skill rules during verification (e.g. areact-best-practicesskill may define what "delivered" means for React code).
Evidence types
Every claim in VERIFICATION.md names exactly one of these types:
command— exact command, cwd, and observed output.source-audit—path:lineor the exact search query proving a static property.browser— route, interaction performed, what was observed (screenshot path if captured).artifact— a generated file, report, or document; cite its path.external-source— URL, issue, or doc page used as authority.N/A: <reason>— why an outcome or decision row does not apply.
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 · 129 lines · 61 tokens per session scan A cc735f044fe9
jira-verifier is an agent published in the GitHub repository koolamusic/claudefiles (131 stars, last pushed 8d ago), licensed MIT. It adds 61 tokens to every session and 1,924 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…