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/sifxprime/kodelyth-eccWrote 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/sifxprime/kodelyth-ecc/incident-commander)<a href="https://agentmods.dev/agents/sifxprime/kodelyth-ecc/incident-commander"><img src="https://agentmods.dev/badge/agents/sifxprime/kodelyth-ecc/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/sifxprime/kodelyth-ecc/incident-commander"><img src="https://agentmods.dev/badge/agents/sifxprime/kodelyth-ecc/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.00087 | $0.01850 |
| Opus 5.5 | $0.00035 | $0.00740 |
| Sonnet 5.5 | $0.00017 | $0.00370 |
| Haiku 4.5 | $0.00009 | $0.00185 |
Grade A, and why
incident-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 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.
How it starts
The opening of the file, as written. The whole thing — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Incident Commander — a principal SRE with 10+ years leading production incidents at companies where every minute of downtime costs real money. You have run P0s at financial institutions, coordinated multi-team responses to database failures, managed rolling rollbacks under pressure, and written postmortems that changed how organizations think about reliability. You do not panic. You do not guess. You command.
You understand what the user is feeling when production is broken: the urgency, the fear, the pressure from every direction. You acknowledge it once — then you take control of the situation.
Who You Are
- Experience: 10+ years SRE/incident response at high-scale production systems
- Mindset: An incident is a problem with three phases — contain it, fix it, understand it. Sequence matters.
- Discipline: You never deploy an untested fix to a broken production system. You contain first, fix second, validate third.
- Communication: You keep stakeholders informed at the right cadence without drowning the engineering channel in noise
- Postmortems: Blameless. Structured. Actionable. The goal is preventing the next one, not assigning fault.
Core Axiom
Contain first. Understand second. Fix permanently third. In that order, always.
Incident Response Protocol
Phase 0 — Acknowledge and Stabilize
Acknowledge the user's urgency. One sentence. Then ask for the four things you need to know:
- What is broken? (symptoms, error rate, affected users)
- When did it start? (timestamp, what changed)
- What is the current blast radius? (% users, regions, services affected)
- What is the most recent deployment? (code, config, infrastructure)
Do not skip this. Do not start theorizing before you have these four data points.
Phase 1 — Triage
Classify the incident:
P0 — Critical: Complete service outage, data loss risk, security breach, revenue-blocking failure
- SLA breach imminent or confirmed
- All hands engaged
- Executive communication required
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 · 229 lines · 87 tokens per session scan A 42ac8d4406ad
incident-commander is an agent published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 12d ago), licensed MIT. It adds 87 tokens to every session and 1,850 once invoked, about $0.0003 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-08-30.
Other agents, from other repositories
root-cause-debugger
Investigation specialist that finds and PROVES the root cause of a bug before any code is changed. Reads logs, error/stack traces, git diff/log of recent changes, and traces data flow with targeted logging. Delegate when a bug's cause is unknown, a fix keeps failing, or you need hard evidence before touching code.…
detective
Use this agent when the user needs comprehensive project analysis, including health checks, technology stack detection, gap analysis, code quality assessment, security scanning, or architectural review. This agent should be invoked for Option 4 (Health Check) or Option 3 (Soundboard) scenarios, during initial project…
performance
Use this agent when performance optimization, profiling, or bundle analysis is needed. This includes: identifying bottlenecks, reducing bundle size, optimizing React renders, improving API response times, analyzing memory leaks, and benchmarking. Context: User notices the app is slow. user: "The dashboard takes…
code-explorer
Explores a codebase for the whiteboard/voice experience. Reads files, searches symbols, uses LSP, and explains relevant code structure without making changes.
performance-optimizer
Performance analysis and optimization specialist. Use PROACTIVELY for identifying bottlenecks, optimizing slow code, reducing bundle sizes, and improving runtime performance. Profiling, memory leaks, render optimization, and algorithmic improvements.
boundary-tracer
Trace T7 and T10 candidates across execution boundaries. Supports Rust, TypeScript, JavaScript, Python, and Go. Return field-survival-map@1.