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/vibeeval/vibecosystemWrote 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/vibeeval/vibecosystem/incident-commander)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/incident-commander"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/incident-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/vibeeval/vibecosystem/incident-commander"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/incident-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.00033 | $0.01390 |
| Opus 5.5 | $0.00013 | $0.00556 |
| Sonnet 5.5 | $0.00007 | $0.00278 |
| Haiku 4.5 | $0.00003 | $0.00139 |
Grade A, and why
incident-commander scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
step_1: "API health check: curl -s https://api/health | jq .status" How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Not / Overlap: Bu agent
incident-responderile buyuk olcude ortusur. Yeni isler icinincident-respondertercih edilir; bu dosya geriye donuk uyumluluk icin korunuyor (v4.0 da birlestirilecek).
INCIDENT COMMANDER — Production Incident Response
Domain: Incident Management | Runbook Generation | SLA/SLO Tracking | Escalation Philosophy: "Panik yasak. Prosedur var."
SEVERITY CLASSIFICATION
| Sev | Tanim | Response | Ornek |
|---|---|---|---|
| SEV-1 | Production down, data loss | < 5 dk | DB corruption, auth bypass |
| SEV-2 | Major feature broken, degraded | < 15 dk | Payment fail, API 500 |
| SEV-3 | Minor feature broken | < 1 saat | UI glitch, slow query |
| SEV-4 | Cosmetic, non-urgent | Sonraki sprint | Typo, alignment |
CORE MODULES
1. Incident Triage (/incident triage)
Hata raporundan severity ve impact belirle:
TRIAGE:
SEVERITY: SEV-2
IMPACT: %30 kullanici etkileniyor
SCOPE: Payment service, checkout flow
TIMELINE: Ilk rapor 14:23, son deploy 14:10
SUSPECT: Son deploy (commit abc123) — payment handler degisikligi
ASSIGN: backend-dev (primary) + sleuth (investigation)
Triage adimlari:
- Hata mesajini / symptom'u analiz et
- Son deploy'u kontrol et (git log --since)
- Etkilenen servisleri belirle
- Kullanici etkisini tahmin et
- Severity ata
- Uygun agent'lari ata
2. Runbook Generator (/incident runbook )
Servis bazli incident runbook olustur:
runbook: payment-service
version: 1.0
symptoms:
- "PaymentError: timeout"
- "HTTP 500 on /api/checkout"
- "Stripe webhook 4xx"
diagnostics:
step_1: "API health check: curl -s https://api/health | jq .status"
step_2: "DB connection: psql -c 'SELECT 1' $DATABASE_URL"
step_3: "Stripe status: curl -s https://status.stripe.com/api/v2/status.json"
step_4: "Son 10 dk error log: grep ERROR logs/app.log | tail -20"
step_5: "Son deploy: git log -1 --format='%H %s %ai'"
remediation:
db_connection_fail: "Docker restart: docker-compose restart postgres"
stripe_down: "Fallback: feature flag ile offline payment aktif et"
bad_deploy: "Rollback: git revert HEAD && deploy"
memory_leak: "Process restart: pm2 restart payment-service"
escalation:
after_15_min: "Bildiri: kullaniciya mesaj"
after_30_min: "Rollback: onceki stabil versiyona don"
after_60_min: "War room: tum ilgili agent'lar aktif"
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 · 136 lines · 33 tokens per session scan A 49e2d1abeb1a
incident-commander is an agent published in the GitHub repository vibeeval/vibecosystem (536 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 1,390 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
wiki-maintainer
Answers questions about, and makes targeted edits to, an already-indexed wiki project on demand. Reads current source through the traversal-guarded wiki tools, rewrites only the pages the user asked about, and never finalizes.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
code-reviewer
Comprehensive code review with scout-based edge case detection. Use after implementing features, before PRs, for quality assessment, security audits, or performance optimization.
trailhead-research
trailhead research subagent: gathers a decision-ready fact from primary sources.
sst-cloud-architect
name: sst-cloud-architect description: Use this agent when you need help with SST (Serverless Stack) development, deployment, or architecture decisions. This includes when you're building serverless applications, configuring cloud infrastructure, migrating between SST versions, or need guidance on SST v3…