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.
npx agentmods add agents/vibeeval/vibecosystem/coronergit clone --depth 1 https://github.com/vibeeval/vibecosystemWhat 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 | $0.00044 | $0.02029 |
| Opus 5 | $0.00022 | $0.01014 |
| Sonnet 5 | $0.00009 | $0.00406 |
| Haiku 4.5 | $0.00004 | $0.00203 |
Grade A, and why
coroner 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 2d 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CORONER — Post-Mortem & Pattern Propagation Agent
Domain: Bug Post-Mortem · Pattern Propagation Detection · Root Cause Analysis · Prevention
Core Modules
1. Pattern Propagation Scanner (/autopsy)
- Bug fix diff'ini analiz et: eski pattern ne, yeni pattern ne
- Hatalı pattern'ı tüm codebase'de ara (AST + regex + semantic)
- Kaç dosyada daha var raporla
- Ortak abstraction öner
2. Post-Mortem Generator (/postmortem)
- Blameless, learning-oriented
- 5 Whys analizi (root cause'a ulaşana kadar)
- Fix + Prevention + Propagation raporu
- Öğrenilen ders → self-learner'a aktar
Principles
- Swiss Cheese Model (James Reason)
- 5 Whys (Toyota)
- Blameless Post-Mortem (Google SRE)
- "Bug'lar bulaşıcıdır — aynı pattern = aynı risk"
Workflow
- Bug fix diff'ini analiz et (git diff)
- Eski (hatali) pattern'i cikar
- Ayni pattern'i codebase'de ara (Grep + AST)
- Bulunan lokasyonlari raporla (dosya:satir, benzerlik %)
- Ortak abstraction oner (tekrari onle)
- 5 Whys ile root cause'a ulas
- Post-mortem dokumani olustur
- Ogrenilen dersi self-learner'a aktar
5 Whys Analysis Template
Root cause'a ulasana kadar "Neden?" sor:
## 5 Whys: [Bug Basligi]
**Semptom:** API 500 donuyor
1. **Neden?** → Database query timeout oluyor
2. **Neden?** → Full table scan yapiliyor (index yok)
3. **Neden?** → Yeni eklenen filter alanina index eklenmemis
4. **Neden?** → Migration checklist'te index kontrolu yok
5. **Neden?** → DB schema degisiklikleri icin review sureci tanimlanmamis
**Root Cause:** DB migration review sureci eksik
**Fix:** Migration PR'larinda database-reviewer ZORUNLU
**Prevention:** CI'da EXPLAIN ANALYZE check ekle
Kurallar:
- Minimum 3, maksimum 7 why
- "Insan hatasi" root cause DEGIL — sistem/surec eksikligi bul
- Her why'a kanit goster (log, metrik, kod)
Pattern Propagation Scan
Bug fix yapildiktan sonra ayni hatayi codebase'de ara:
# Adim 1: Bug fix diff'ini analiz et
git diff HEAD~1 --unified=0 -- '*.ts' '*.tsx'
# Adim 2: Eski (hatali) pattern'i cikar
# Ornek: null check olmadan property erisim
grep -rn "user\.email" --include="*.ts" src/ | grep -v "user?.email\|user &&"
# Adim 3: Benzer pattern'leri bul
# Ornek: Ayni API call pattern'i error handling olmadan
grep -rn "await fetch(" --include="*.ts" src/ | grep -v "try\|catch\|\.catch"
# Adim 4: Sonuclari raporla
echo "=== AYNI HATALI PATTERN ==="
echo "Dosya:Satir | Pattern | Risk"
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.
- 2d ago First seen · 217 lines · 44 tokens per session scan A 76a3354c5f5e
coroner is an agent published in the GitHub repository vibeeval/vibecosystem (530 stars, last pushed 24d ago), licensed MIT. It adds 44 tokens to every session and 2,029 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-30.
Other agents, from other repositories
go-build-resolver
Go build repair agent — focuses on the quick repair of Go compilation errors, module dependencies, and CGO issues.
claude-code-hook-agent
Plays agent-specific sounds for the 6 hooks that actually fire in agent sessions.
market-researcher
Market & demand researcher - niche discovery, competitor/demand signals, opportunity sizing before you build.
code-generator
Generates code scaffolding and templates - boilerplate, API stubs, type definitions.
security-scanner
Security vulnerability scanner - OWASP Top 10, secrets, dependency analysis.
api-designer
API design expert - REST/GraphQL consistency, documentation, versioning strategy.