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/datum-cloud/claude-code-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/agents/datum-cloud/claude-code-plugins/incident-investigator)<a href="https://agentmods.dev/agents/datum-cloud/claude-code-plugins/incident-investigator"><img src="https://agentmods.dev/badge/agents/datum-cloud/claude-code-plugins/incident-investigator/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/datum-cloud/claude-code-plugins/incident-investigator"><img src="https://agentmods.dev/badge/agents/datum-cloud/claude-code-plugins/incident-investigator.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.00040 | $0.00688 |
| Opus 5.5 | $0.00016 | $0.00275 |
| Sonnet 5.5 | $0.00008 | $0.00138 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
incident-investigator 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 1mo 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 1mo ago First seen · 72 lines · 40 tokens per session scan A af177d2e7e12
incident-investigator is an agent published in the GitHub repository datum-cloud/claude-code-plugins (2 stars, last pushed 5d ago), with no licence file. It adds 40 tokens to every session and 688 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
AWS Incident Triage
On-call SRE agent that drives structured CloudWatch-based incident investigation from alarms through root-cause hypothesis.
cloudbase-deployment-expert
Specializes in CloudBase deployment — cloud function deploy/debug, static hosting upload, CloudRun service management. Use when troubleshooting deployments, checking build logs, or diagnosing runtime errors.
queue-debugger
Use this agent when the user encounters "queue not delivering messages", "consumer errors", "DLQ filling up", "throughput issues", "message backlog", "queue timeout errors", or needs systematic Cloudflare Queues troubleshooting. Examples.
sre
A site reliability engineering agent for keeping production systems available and recoverable. Site reliability engineering applies software practices to operations, incidents, capacity, and monitoring.
infrastructure-maintainer
Use this agent when monitoring system health, optimizing performance, managing scaling, or ensuring infrastructure reliability. This agent excels at keeping studio applications running smoothly while preparing for growth and preventing disasters.
cpln-workload-troubleshooter
Use when a Control Plane workload is unhealthy, crashing, not starting, or behaving unexpectedly. Diagnoses image pull errors, secret access failures, firewall blocks, port mismatches, health check failures, resource limits, and container restrictions.