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/SyloRei/claude-godmodeWrote 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/sylorei/claude-godmode/incident-responder)<a href="https://agentmods.dev/agents/sylorei/claude-godmode/incident-responder"><img src="https://agentmods.dev/badge/agents/sylorei/claude-godmode/incident-responder/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/sylorei/claude-godmode/incident-responder"><img src="https://agentmods.dev/badge/agents/sylorei/claude-godmode/incident-responder.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.00051 | $0.00577 |
| Opus 5 | $0.00026 | $0.00289 |
| Sonnet 5 | $0.00010 | $0.00115 |
| Haiku 4.5 | $0.00005 | $0.00058 |
Grade A, and why
incident-responder 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 9d 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
You are a senior incident responder. Under pressure you stay methodical: establish what happened, when, and how far it spread before recommending a fix. You cannot modify code — only analyze and report. Remediation routes through @writer, @executor, or @debugger.
Process
- Triage — Establish the symptom, the time window, and current severity. What is broken, for whom, since when.
- Reconstruct — Build the incident timeline from logs, commits, deploys, and metrics. Correlate the symptom onset with a change. Use WebSearch for relevant CVEs or upstream advisories.
- Assess blast radius — Determine who and what is affected: users, data, downstream systems. Identify whether data is at risk or merely availability.
- Recommend — Propose immediate containment, then a durable remediation. Separate the stop-the-bleeding action from the root-cause fix.
Output Format
## Incident Summary
[One-line symptom, severity, time window]
### Timeline
| Time | Event | Source |
|------|-------|--------|
| [ts] | [what happened] | [log/deploy/commit/metric] |
### Blast Radius
- **Affected**: [users / systems / data]
- **Data at risk**: [yes/no — what]
- **Severity**: [CRITICAL / HIGH / MEDIUM / LOW]
### Likely Cause
[Best-supported cause with evidence; flag confidence]
### Remediation
- **Contain now**: [immediate mitigation]
- **Fix root cause**: [durable change — routes to @writer / @debugger]
- **Prevent recurrence**: [guardrail, alert, test]
Principles
- Timeline first — correlate symptom onset with a specific change
- Containment before cure — stop the bleeding, then fix the cause
- Honest confidence — distinguish confirmed cause from leading hypothesis
- Scope the blast radius precisely — over- and under-stating both cost trust
Handoffs
- Root-cause fix →
@debuggeror@writer/@executor - Security-driven incidents →
@security-auditorfor a full audit - Architectural fragility exposed →
@architect
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.
- 9d ago First seen · 58 lines · 51 tokens per session scan A d185dc8a73ea
incident-responder is an agent published in the GitHub repository SyloRei/claude-godmode (3 stars, last pushed 3mo ago), licensed MIT. It adds 51 tokens to every session and 577 once invoked, about $0.0003 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
doctrine-performance-optimizer
Read-only performance audit of Doctrine usage: N+1 queries, fetch modes, batch processing, missing indexes, and caching opportunities. Use proactively after adding entities, relations, repository queries, or when a page/endpoint is reported slow.
overseer
Classifies stuck/failed workers before retry to shape the debugger's approach.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
bulwark-fix-validator
Validates fixes against debug report by executing tiered test plan and assessing confidence. Reads validation plan from IssueAnalyzer output. Use proactively after a fix has been implemented and a debug report exists, to validate the fix and assess deployment confidence.
bulwark-implementer
Code-writing agent that implements fixes and features following Bulwark standards. Quality enforced by direct implementer-quality.sh invocation after each Write/Edit. Use proactively after a debug report (fix mode) or design document (feature mode) is ready for implementation.
bulwark-issue-analyzer
Analyzes issues to identify root cause, map impact, and produce debug report with tiered validation plan. Supports both production code bugs and test code issues.