Borrowing it
Nothing to install: this file belongs to Randhir123/claude-ops-investigator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Randhir123/claude-ops-investigator/main/.claude/agents/incident-coordinator.mdgit clone --depth 1 https://github.com/Randhir123/claude-ops-investigatorWrote 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/randhir123/claude-ops-investigator/incident-coordinator)<a href="https://agentmods.dev/agents/randhir123/claude-ops-investigator/incident-coordinator"><img src="https://agentmods.dev/badge/agents/randhir123/claude-ops-investigator/incident-coordinator/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/randhir123/claude-ops-investigator/incident-coordinator"><img src="https://agentmods.dev/badge/agents/randhir123/claude-ops-investigator/incident-coordinator.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.00054 | $0.01910 |
| Opus 5.5 | $0.00022 | $0.00764 |
| Sonnet 5.5 | $0.00011 | $0.00382 |
| Haiku 4.5 | $0.00005 | $0.00191 |
Grade A, and why
incident-coordinator 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 26d 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.
- 26d ago Changed · +9 lines ed8dfa226475
- 1mo ago First seen · 143 lines · 54 tokens per session scan A d03dd166d6ef
incident-coordinator is an agent published in the GitHub repository Randhir123/claude-ops-investigator (1 stars, last pushed 26d ago), with no licence file. It adds 54 tokens to every session and 1,910 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-08-31.
Other agents, from other repositories
cicd-automation-devops-troubleshooter
Expert DevOps troubleshooter specializing in rapid incident response, advanced debugging, and modern observability. Masters log analysis, distributed tracing, Kubernetes debugging, performance optimization, and root cause analysis. Handles production outages, system reliability, and preventive monitoring. Use…
devops-troubleshooter
Debug production issues, analyze logs, and fix deployment failures. Masters monitoring tools, incident response, and root cause analysis. Use PROACTIVELY for production debugging or system outages.
container-build
Container build and debugging. Builds Docker images, analyzes build failures, inspects layers, and troubleshoots container issues. Use for Docker/container operations.
docker-debug
Container troubleshooting specialist.
megalinter-runner
Run MegaLinter locally with npx mega-linter-runner (full flavor run or standalone single-linter image), digest the reports, and return only a compact error list. Use to keep verbose linter output out of the main context. Runs and reports only — never fixes source files.
staff-infrastructure
Staff infrastructure engineer expert in Terraform, AWS, Docker, shell scripting, Python, CI/CD, GitHub Actions, logging, monitoring, and production debugging. Use proactively for infrastructure, deployment, Docker, CI/CD, scripting, and observability tasks.