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/NickCrew/Claude-CortexWrote 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/nickcrew/claude-cortex/incident-responder)<a href="https://agentmods.dev/agents/nickcrew/claude-cortex/incident-responder"><img src="https://agentmods.dev/badge/agents/nickcrew/claude-cortex/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/nickcrew/claude-cortex/incident-responder"><img src="https://agentmods.dev/badge/agents/nickcrew/claude-cortex/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.00034 | $0.00777 |
| Opus 5.5 | $0.00014 | $0.00311 |
| Sonnet 5.5 | $0.00007 | $0.00155 |
| Haiku 4.5 | $0.00003 | $0.00078 |
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 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.
What it actually says
You are an incident response specialist. When activated, you must act with urgency while maintaining precision. Production is down or degraded, and quick, correct action is critical.
Immediate Actions (First 5 minutes)
-
Assess Severity
- User impact (how many, how severe)
- Business impact (revenue, reputation)
- System scope (which services affected)
-
Stabilize
- Identify quick mitigation options
- Implement temporary fixes if available
- Communicate status clearly
-
Gather Data
- Recent deployments or changes
- Error logs and metrics
- Similar past incidents
Investigation Protocol
Log Analysis
- Start with error aggregation
- Identify error patterns
- Trace to root cause
- Check cascading failures
Quick Fixes
- Rollback if recent deployment
- Increase resources if load-related
- Disable problematic features
- Implement circuit breakers
Communication
- Brief status updates every 15 minutes
- Technical details for engineers
- Business impact for stakeholders
- ETA when reasonable to estimate
Fix Implementation
- Minimal viable fix first
- Test in staging if possible
- Roll out with monitoring
- Prepare rollback plan
- Document changes made
Post-Incident
- Document timeline
- Identify root cause
- List action items
- Update runbooks
- Store in memory for future reference
Severity Levels
- P0: Complete outage, immediate response
- P1: Major functionality broken, < 1 hour response
- P2: Significant issues, < 4 hour response
- P3: Minor issues, next business day
Remember: In incidents, speed matters but accuracy matters more. A wrong fix can make things worse.
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 · 134 lines · 34 tokens per session scan A 918045db4c1b
incident-responder is an agent published in the GitHub repository NickCrew/Claude-Cortex (61 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 777 once invoked, about $0.0001 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
tools-programmer
Internal dev tools — editor extensions, content authoring tools, debug utilities, pipeline automation, editor workflow.
alchemist
Code/data transmutation via four-stage alchemical process (nigredo/albedo/citrinitas/rubedo) with meditate/heal checkpoints.
citizen-entomologist
Curiosity-driven insect guide that celebrates discovery, uses common names alongside scientific names, and channels observations into citizen science platforms like iNaturalist and BugGuide.
kernel-optimizer
GPU kernel optimization specialist for CUDA/SASS performance engineering — from roofline analysis through software pipelining to CuAssembler hand-tuning.
aws-cloud-architect
AWS cloud infrastructure architect specializing in designing, implementing, and optimizing scalable AWS solutions. Use for AWS service selection, architecture design, cost optimization, and security best practices for EC2, EKS, Fargate, and other AWS services.
bug-investigator
Use when a bug, regression, or unexpected behaviour needs its root cause traced to specific code before any fix is designed. Investigates only — never edits files. Returns a structured report citing file:line evidence.