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.
git clone --depth 1 https://github.com/redhat-et/rhdp-rca-pluginWrote 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/redhat-et/rhdp-rca-plugin/incident-investigator-agent)<a href="https://agentmods.dev/agents/redhat-et/rhdp-rca-plugin/incident-investigator-agent"><img src="https://agentmods.dev/badge/agents/redhat-et/rhdp-rca-plugin/incident-investigator-agent/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.
<a href="https://agentmods.dev/agents/redhat-et/rhdp-rca-plugin/incident-investigator-agent"><img src="https://agentmods.dev/badge/agents/redhat-et/rhdp-rca-plugin/incident-investigator-agent.svg" alt="Reviewed on agentmods" width="80" 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.00076 | $0.00353 |
| Opus 5 | $0.00038 | $0.00177 |
| Sonnet 5 | $0.00015 | $0.00071 |
| Haiku 4.5 | $0.00008 | $0.00035 |
Grade A, and why
incident-investigator-agent 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 12d 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.
What it actually says
Your Mission
You orchestrate end-to-end incident investigations workflow by coordinating a three-phase pipeline that systematically gathers evidence, analyzes patterns, and enriches findings with contextual information. You transform raw signals into actionable insights that help teams understand what happened, why it happened, and how to prevent recurrence.
- Phase 1 [logs-fetcher] Fetch logs via SSH
- Phase 2 [root-cause-analysis] Analyze logs and correlate with Splunk
- Phase 3 [context-fetcher] Fetch additional context if needed
Phase 1: Fetch Logs
Use log-fetcher.
Phase 2: Perform Root Cause Analysis
Use root-cause-analysis.
Phase 3: Fetch contexts
Use context-fetcher.
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.
- 12d ago First seen · 42 lines · 76 tokens per session scan A bdddc4389a11
incident-investigator-agent is an agent published in the GitHub repository redhat-et/rhdp-rca-plugin (11 stars, last pushed 17d ago), licensed Apache-2.0. It adds 76 tokens to every session and 353 once invoked, about $0.0004 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-31.
Other agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.
evidence_ingestion_agent
An agent that gathers the facts needed to investigate a failure, including error messages, software versions, environment details, reproduction steps, inputs, expected results, actual results, and timing.