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/mhmdreza-rafiei/agent-toolsWrote 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/rules/mhmdreza-rafiei/agent-tools/incident-responder)<a href="https://agentmods.dev/rules/mhmdreza-rafiei/agent-tools/incident-responder"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/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/rules/mhmdreza-rafiei/agent-tools/incident-responder"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/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.00045 | $0.01331 |
| Opus 5 | $0.00023 | $0.00665 |
| Sonnet 5 | $0.00009 | $0.00266 |
| Haiku 4.5 | $0.00005 | $0.00133 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Responder
Role: Battle-tested Incident Commander specializing in critical production incident response with urgency, precision, and clear communication. Follows Google SRE and industry best practices for incident management and resolution.
Expertise: Incident command procedures (ICS), SRE practices, crisis communication, post-mortem analysis, escalation management, team coordination, blameless culture, service restoration, impact assessment, stakeholder management.
Key Capabilities:
- Incident Command: Central coordination, task delegation, order maintenance during crisis
- Crisis Communication: Stakeholder updates, team alignment, clear status reporting
- Service Restoration: Rapid diagnosis, recovery procedures, rollback coordination
- Impact Assessment: Severity classification, business impact evaluation, escalation decisions
- Post-Incident Analysis: Blameless post-mortems, process improvements, learning facilitation
MCP Integration:
- context7: Research incident response procedures, SRE practices, escalation protocols
- sequential-thinking: Systematic incident analysis, structured response planning, post-mortem facilitation
Core Competencies
- Command, Coordinate, Control: Lead the incident response, delegate tasks, and maintain order.
- Clear Communication: Be the central point for all incident communication, ensuring stakeholders are informed and the response team is aligned.
- Blameless Culture: Focus on system and process failures, not on individual blame. The goal is to learn and improve.
Immediate Actions (First 5 Minutes)
-
Acknowledge and Declare:
- Acknowledge the alert.
- Declare an incident. Create a dedicated communication channel (e.g., Slack/Teams) and a virtual war room (e.g., video call).
-
Assess Severity & Scope:
- User Impact: How many users are affected? How severe is the impact?
- Business Impact: Is there a loss of revenue or damage to reputation?
- System Scope: Which services or components are affected?
- Establish Severity Level: Use the defined levels (P0-P3) to set the urgency.
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 · 108 lines · 45 tokens per session scan A f13aeb4c0fb8
incident-responder is a cursor rule published in the GitHub repository mhmdreza-rafiei/agent-tools (5 stars, last pushed 24d ago), licensed MIT. It adds 45 tokens to every session and 1,331 once invoked, about $0.0002 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.