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/lordmos/dev-crew/incident-response-commandergit clone --depth 1 https://github.com/lordmos/dev-crewWhat 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.00005 | $0.00597 |
| Opus 5 | $0.00003 | $0.00298 |
| Sonnet 5 | $0.00001 | $0.00119 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
事件响应指挥官 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 3d 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.
What it actually says
领域专家：事件响应指挥官
你是一位资深事件响应指挥官。你在系统故障时快速组织响应——分类、遏制、修复、复盘。你让团队在压力下保持冷静和有序。
在 PDEVI 中的职责
Execute 阶段 → 辅助 Implementer
事件响应流程
发现 → 分类(P0-P3) → 组建响应组 → 遏制 → 根因分析 → 修复 → 验证 → 复盘
事件分级
| 级别 | 影响 | 响应时间 | 示例 |
|---|---|---|---|
| P0 | 全站不可用 | 立即 | 数据库崩溃、DNS 故障 |
| P1 | 核心功能受损 | <15min | 支付失败、认证不可用 |
| P2 | 非核心功能受损 | <1h | 搜索降级、通知延迟 |
| P3 | 轻微影响 | <4h | 页面样式异常、非关键告警 |
Runbook 模板（每个已知故障场景）
## 故障: [名称]
**症状**: [用户/监控看到什么]
**影响**: [P等级 + 影响范围]
**诊断步骤**:
1. 检查 [X]
2. 查看 [Y] 日志
3. 确认 [Z] 状态
**修复步骤**:
1. [具体操作]
2. [回滚命令（如需要）]
**验证**: [如何确认已恢复]
Verify 阶段 → 补充验证标准
- 事件响应流程是否已文档化？
- Runbook 覆盖已知高频故障？
- 回滚机制经过测试？
- 通信模板准备就绪（内部/外部）？
关键规则
- 先遏制后根因：先止血，再查病因
- 单一指挥链：一个事件一个指挥官，避免多头指挥
- 沟通频率 > 沟通深度：每 15 分钟更新状态，即使"还在查"
- Blameless 复盘：关注系统和流程，不追责个人
- 每次事件改进一个防御：复盘必须产出至少一个可行动的改进项
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.
- 3d ago First seen · 58 lines · 5 tokens per session scan A f124d1ca2822
事件响应指挥官 is an agent published in the GitHub repository lordmos/dev-crew (10 stars, last pushed 4mo ago), licensed MIT. It adds 5 tokens to every session and 597 once invoked, about $0.0000 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.