What is investigate-finding?

A command that investigates one Blumira finding, including its severity, evidence, surrounding context, and comment history.

Use it to review a finding in depth, follow investigation notes, and identify recommended next steps or resolution actions.

It gathers the information needed to understand an alert without opening several records and timelines separately.

investigate-finding — Command for Claude Code by WYRE-AI

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/WYRE-AI/msp-claude-plugins

Made for: Claude Code.

Or install blumira, the plugin that ships this one along with the rest of its 4 skills, 6 commands, 2 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/commands/wyre-ai/msp-claude-plugins/investigate-finding/github.svg)](https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/investigate-finding)

Your own site

<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/investigate-finding"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/investigate-finding/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/wyre-ai/msp-claude-plugins/investigate-finding"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/investigate-finding.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 348 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.00348
Opus 5	$0.00008	$0.00174
Sonnet 5	$0.00003	$0.00070
Haiku 4.5	$0.00002	$0.00035

Measured 5d ago against content hash 74b4a96bd748, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

investigate-finding 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 5d 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.

msp-claude-plugins/blumira/blumira/commands/investigate-finding.md · 50 lines

What it actually says