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.
npx agentmods add commands/wyre-ai/msp-claude-plugins/resolve-findinggit clone --depth 1 https://github.com/WYRE-AI/msp-claude-pluginsWrote 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/commands/wyre-ai/msp-claude-plugins/resolve-finding)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/resolve-finding"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/resolve-finding.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 | $0.00012 | $0.00434 |
| Opus 5 | $0.00006 | $0.00217 |
| Sonnet 5 | $0.00002 | $0.00087 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
resolve-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 yesterday.
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.
What it actually says
Resolve Finding
Prerequisites
- Valid Blumira JWT token configured
- Finding ID and investigation context
Steps
- Call
blumira_findings_getto confirm the finding exists and review its current status - Map the resolution type argument to the numeric code:
valid→ 10not-applicable→ 20false-positive→ 30
- Add an investigation comment with
blumira_findings_comments_adddocumenting the resolution rationale - Call
blumira_findings_resolvewith the finding ID, resolution type code, and notes - Confirm resolution was successful
- Report the updated finding status
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| finding_id | string | Yes | UUID of the finding to resolve |
| resolution_type | string | Yes | One of: valid, not-applicable, false-positive |
| notes | string | Yes | Explanation of the resolution decision |
Examples
Resolve as Valid
/resolve-finding --finding_id "a1b2c3d4-..." --resolution_type valid --notes "Confirmed brute force. Source IP blocked."
Resolve as False Positive
/resolve-finding --finding_id "a1b2c3d4-..." --resolution_type false-positive --notes "Scheduled backup job triggers this alert."
Error Handling
- Already resolved: Report current resolution status
- Invalid resolution type: Show valid options (valid, not-applicable, false-positive)
- Finding not found: Suggest using
/finding-triageto find valid IDs
Related Commands
/investigate-finding- Investigate before resolving/finding-triage- Find findings that need resolution
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.
- yesterday First seen · 58 lines · 12 tokens per session scan A 82d773af0468
resolve-finding is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (44 stars, last pushed 2d ago), licensed Apache-2.0. It adds 12 tokens to every session and 434 once invoked, about $0.0001 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-09-04.
Other commands, from other repositories
research_codebase
Document codebase as-is with thoughts directory for historical context.
create_handoff
Create handoff document for transferring work to another session.
statusline-install
Add the backlog badge (📋 N open items) to the Claude Code statusLine. Wraps an existing statusLine if you have one, creates it otherwise. Edits /.claude/settings.json (or $CLAUDECONFIGDIR).
iterate_plan
Iterate on existing implementation plans with thorough research and updates.
speckit.verify-tasks
Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).
speckit.git.initialize
Initialize a Git repository with an initial commit.