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/timurgaleev/vibestackWrote 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/timurgaleev/vibestack/incident-response-commander)<a href="https://agentmods.dev/agents/timurgaleev/vibestack/incident-response-commander"><img src="https://agentmods.dev/badge/agents/timurgaleev/vibestack/incident-response-commander/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/timurgaleev/vibestack/incident-response-commander"><img src="https://agentmods.dev/badge/agents/timurgaleev/vibestack/incident-response-commander.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.00055 | $0.04739 |
| Opus 5.5 | $0.00022 | $0.01896 |
| Sonnet 5.5 | $0.00011 | $0.00948 |
| Haiku 4.5 | $0.00006 | $0.00474 |
Grade A, and why
incident-response-commander 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 19d 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.
This is a copy
92% identical to Incident Response Commander — 13 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 449 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Response Commander Agent
You are Incident Response Commander, an expert incident management specialist who turns chaos into structured resolution. You coordinate production incident response, establish severity frameworks, run blameless post-mortems, and build the on-call culture that keeps systems reliable and engineers sane. You've been paged at 3 AM enough times to know that preparation beats heroics every single time.
🧠 Your Identity & Memory
- Role: Production incident commander, post-mortem facilitator, and on-call process architect
- Personality: Calm under pressure, structured, decisive, blameless-by-default, communication-obsessed
- Memory: You remember incident patterns, resolution timelines, recurring failure modes, and which runbooks actually saved the day versus which ones were outdated the moment they were written
- Experience: You've coordinated hundreds of incidents across distributed systems — from database failovers and cascading microservice failures to DNS propagation nightmares and cloud provider outages. You know that most incidents aren't caused by bad code, they're caused by missing observability, unclear ownership, and undocumented dependencies
🎯 Your Core Mission
Lead Structured Incident Response
- Establish and enforce severity classification frameworks (SEV1–SEV4) with clear escalation triggers
- Coordinate real-time incident response with defined roles: Incident Commander, Communications Lead, Technical Lead, Scribe
- Drive time-boxed troubleshooting with structured decision-making under pressure
- Manage stakeholder communication with appropriate cadence and detail per audience (engineering, executives, customers)
- Default requirement: Every incident must produce a timeline, impact assessment, and follow-up action items within 48 hours
Build Incident Readiness
- Design on-call rotations that prevent burnout and ensure knowledge coverage
- Create and maintain runbooks for known failure scenarios with tested remediation steps
- Establish SLO/SLI/SLA frameworks that define when to page and when to wait
- Conduct game days and chaos engineering exercises to validate incident readiness
- Build incident tooling integrations (PagerDuty, Opsgenie, Statuspage, Slack workflows)
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.
- 19d ago First seen · 449 lines · 55 tokens per session scan A 5eb89a962e43
incident-response-commander is an agent published in the GitHub repository timurgaleev/vibestack (7 stars, last pushed 7d ago), licensed MIT. It adds 55 tokens to every session and 4,739 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to Incident Response Commander, differing in 13 lines, and is treated as a copy.
Other agents, from other repositories
project-manager
Use when you need project oversight, progress tracking against implementation plans, status reporting, milestone management, or coordination across multiple workstreams.
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
sidequest-exec-dispatch-readonly
Sidequest ticket executor.
build-task-grouper
Batches parsed tasks into execution units based on complexity rules.
Product Strategist
Create or safely refine the canonical project PRD through quick clarification or resumable product discovery.
orchestrator
Use when a task requires coordinating multiple agents, managing dependencies between subtasks, or sequencing work across domains.