A command for researching a development task and recording a structured assessment in the project’s issue tracker. It reads the task, project guidance, and relevant code context before development begins.

Use it with an issue or ticket that has a description. It can inspect GitHub or JIRA tasks, read project context, and stop when the issue is missing a description or already contains research findings.

It helps reveal the likely impact of a change and preserves the findings where the development work is tracked.

How xsovad06/sova configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to xsovad06/sova. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/xsovad06/sova/main/.claude/commands/research.md

Clone the repo

git clone --depth 1 https://github.com/xsovad06/sova

Made for: Claude Code.

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/commands/xsovad06/sova/research/github.svg)](https://agentmods.dev/commands/xsovad06/sova/research)

Your own site

<a href="https://agentmods.dev/commands/xsovad06/sova/research"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/research/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/commands/xsovad06/sova/research"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 16 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,462 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.00016	$0.01462
Opus 5.5	$0.00006	$0.00585
Sonnet 5.5	$0.00003	$0.00292
Haiku 4.5	$0.00002	$0.00146

Measured 14d ago against content hash 4e083b7e5424, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

research 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 14d 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.

.claude/commands/research.md · 175 lines

How it starts

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

Research

Investigate a task's codebase impact and produce a structured research assessment. Designed for autonomous execution: always writes findings back to the tracker. For interactive pre-development planning, use the /spec workflow instead.

Task: $ARGUMENTS

Instructions

Step 1: Fetch the Task

Get the issue number or ticket key from $ARGUMENTS. If empty, stop with an error.

Determine the task source by running sova config and reading the task_source row (configuration lives in .claude/sova.db, not in a file).

GitHub (the default):

gh issue view $ARGUMENTS --json number,title,body,labels,milestone

JIRA (task_source.type = "jira"):

jira issue view $ARGUMENTS --plain

Save the original description verbatim.

If the issue has no description or body, report "Issue has no description; needs specification before research" and stop.

If the issue body already contains a ## Research section, report "Issue already has a research section; ready for development" and stop.

Step 2: Read Project Context

Read whatever exists; skip files that are missing:

CLAUDE.md and AGENTS.md for project conventions
.claude/rules/architecture.md for component overview and design decisions
The cookbook for known patterns and past mistakes: the README.md index of .claude/agent-memory/cookbook/ plus the domain files relevant to this task when that directory exists, otherwise .claude/agent-memory/cookbook.md; also .claude/agent-memory/common-mistakes.md if present

Step 3: Explore the Codebase

Based on the issue, investigate the affected areas. Use file reads, grep, and search; do not guess from file names alone.

Identify affected files: find every file that needs to be modified, created, or deleted. Read the actual source to confirm.
Find the pattern: locate the closest existing implementation to follow. Note specific file paths, class names, and method signatures.
Check for data model changes: determine if DB models, schemas, or migrations are needed.
Check for API changes: identify new or modified endpoints with request/response shapes.
Find reusable code: identify utilities, base classes, test fixtures, and patterns that the implementation should use. Reference specific functions and classes.
Anticipate edge cases: based on reading the actual code, identify failure modes and edge cases not obvious from the issue description.
Check for UI implications: templates, components, user-facing behavior changes.
Design implementation approach: produce a concrete 3-6 step plan referencing specific files.

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

14d ago Changed 4e083b7e5424
16d ago Changed · +6 lines 9270d15643ca
21d ago Changed d4be1b9edd49
1mo ago Changed cd1cf8cd7222
2mo ago First seen · 169 lines · 16 tokens per session scan A 18b0c79685ea

Subscribe to this mod's changes

research is a command published in the GitHub repository xsovad06/sova (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 16 tokens to every session and 1,462 once invoked, about $0.0001 per session on Opus 5.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-31.

Code review Planning Research ai-agents automation autonomous-development cli core developer-tools

sova: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Research

Instructions

Step 1: Fetch the Task

Step 2: Read Project Context

Step 3: Explore the Codebase

What this file has done since we first saw it

Other commands, from other repositories

greptile-review

review-branch

review

advanced-code-review-context

code-review-give

mach12:issue-review