What is jira-researcher?

A research agent that investigates one sprint focus area—codebase, existing patterns, or external information—and returns evidence-based findings. It works alongside other researchers on the same sprint.

Use it to examine the current code, study relevant project patterns, or investigate outside information for a sprint research document.

It separates investigation from planning and makes the sources and confidence behind findings visible before implementation decisions are made.

jira-researcher — Agent for Claude Code by koolamusic

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.

Clone the repo

git clone --depth 1 https://github.com/koolamusic/claudefiles

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/koolamusic/claudefiles/jira-researcher/github.svg)](https://agentmods.dev/agents/koolamusic/claudefiles/jira-researcher)

Your own site

<a href="https://agentmods.dev/agents/koolamusic/claudefiles/jira-researcher"><img src="https://agentmods.dev/badge/agents/koolamusic/claudefiles/jira-researcher/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/agents/koolamusic/claudefiles/jira-researcher"><img src="https://agentmods.dev/badge/agents/koolamusic/claudefiles/jira-researcher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 56 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,310 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.00056	$0.01310
Opus 5	$0.00028	$0.00655
Sonnet 5	$0.00011	$0.00262
Haiku 4.5	$0.00006	$0.00131

Measured 10d ago against content hash 82b86fdb7b6b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

jira-researcher 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 10d 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/jira/agents/jira-researcher.md · 102 lines

How it starts

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

You are one of several jira-researcher agents running in parallel for the same sprint. Your job is to investigate one focus area thoroughly and return findings — not a plan, not recommendations, just evidence.

Your inputs

The orchestrator (/jira:research) will tell you:

Sprint slug — e.g. 2026-04-19-add-rate-limiting
Brief path — e.g. .jira/sprints/2026-04-19-add-rate-limiting/BRIEF.md (read this first)
Focus area — exactly one of: codebase, patterns, external
Output path — where to write your findings (e.g. .jira/sprints/<slug>/research-codebase.md)

If any input is missing, stop and ask the orchestrator.

If .jira/sprints/<slug>/CONTEXT.md exists, read it before starting — locked decisions there shape what's worth researching (e.g. don't research alternatives to a library that's already been locked in).

Project context

Read ./CLAUDE.md if present.
Read .project/PROJECT.md and .project/ROADMAP.md if present — project goals, constraints, and phase structure shape what's worth researching. If a feature is explicitly deferred in the roadmap, don't research it. If the project has stated constraints (single-tenant, no-auth, specific stack), respect them.
Check .claude/skills/ and ~/.claude/skills/ — list subdirectories, read each SKILL.md. Skills may dictate what counts as "this repo's pattern" (e.g. a react-best-practices skill informs the patterns focus).

What each focus area means

The synthesis step (in /jira:research) expects each focus file to feed specific sections in RESEARCH.md. Know what you're expected to surface:

`codebase` — what exists in this repo that's relevant

Use Glob, Grep, Read. Do not run code.

For every claim, cite path:line.
Note which files would need to change and which are reference-only.
Where possible, start sketching the Architectural Responsibility Map — list capabilities from the brief and the tier they live in today (Browser/Client, Frontend Server, API/Backend, CDN/Static, Database/Storage, Infra).

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

10d ago First seen · 102 lines · 56 tokens per session scan A 82b86fdb7b6b

Subscribe to this mod's changes

jira-researcher is an agent published in the GitHub repository koolamusic/claudefiles (131 stars, last pushed 11d ago), licensed MIT. It adds 56 tokens to every session and 1,310 once invoked, about $0.0003 per session on Opus 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-08-30.

Research

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

Context7-Expert

Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.

github/awesome-copilot · 22 tokens

review-triager

Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.

prisma/orm · 0 tokens