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/sifxprime/kodelyth-ecc/incident-commandergit 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.svg" alt="Measured on agentmods" 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 | $0.00087 | $0.01850 |
| Opus 5 | $0.00044 | $0.00925 |
| Sonnet 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 4d 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.
- 4d 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 2d ago), licensed MIT. It adds 87 tokens to every session and 1,850 once invoked, about $0.0004 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
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
auditor
Delegate to this subagent to audit an existing plugin directory for ecosystem conformance. Input is the plugin directory path. Checks: plugin.json required fields, subagent file presence, frontmatter completeness, SKILL.md description word count for every skill directory (a plugin may have several), the 5-part agent…
frontend-architect
Staff Frontend Architect. Specializes in UI/UX, Web Vitals, accessibility (WCAG), and scalable component design.
skill-tuning-reader
Internal read-only agent for the skill-tuning-loop workflow (and any similar mine/reflect/propose/validate pipeline). Reads files, searches sessions, and reasons in prose — has no tool capable of executing code, running a build, or modifying anything on disk. Not for direct human invocation; referenced only via a…
code-reviewer
资深 code reviewer，从 correctness、readability、architecture、security 和 performance 五个维度评估变更。用于合并前的 thorough code review。.
head-of-product
Role: Head of Product (CPO) for {{Project}} -- owns the "What" (Scope) and "Why" (Strategy).