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 skills add event4u-app/agent-config --skill incident-commandergit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/skills/event4u-app/agent-config/incident-commander)<a href="https://agentmods.dev/skills/event4u-app/agent-config/incident-commander"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/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/skills/event4u-app/agent-config/incident-commander"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/incident-commander.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00048 | $0.01435 |
| Opus 5 | $0.00024 | $0.00718 |
| Sonnet 5 | $0.00010 | $0.00287 |
| Haiku 4.5 | $0.00005 | $0.00144 |
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 9d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
incident-commander
Run the coordination layer during an incident: classify severity, set comms cadence, hold a clean timeline, and draft the post-mortem skeleton when the dust settles. This skill does not debug the system — that is the engineer's job. The commander keeps the room oriented so the engineer can think.
When to use
- Production is degraded or down and someone needs to coordinate.
- A critical job, queue, or third-party is failing and the team is scrambling.
- A near-miss happened and a post-mortem is being drafted.
- German triggers: "Vorfall", "Prod ist down", "wer übernimmt Comms?".
Do NOT use when:
- The system is healthy and the concern is a future outage —
route to
risk-officerinstead. - The user wants the bug fixed — route to
/bug-investigateand/bug-fix. The commander coordinates; engineers debug. - The incident is a security breach — route to
threat-modelingfirst; the commander still runs comms but the response shape changes.
Procedure
1. Inspect the signal and classify severity
| SEV | Trigger |
|---|---|
| SEV-1 | User-facing outage, data loss risk, revenue impact |
| SEV-2 | Major degradation, workaround exists |
| SEV-3 | Single-feature broken, low blast radius |
| SEV-4 | Internal-only, not user-visible |
Pick the highest SEV any signal supports. Downgrades happen later with evidence; never start low to avoid noise.
2. Set the comms cadence
- Internal channel — single thread; no side-channels.
- Update interval — SEV-1 every 15 min, SEV-2 every 30 min, SEV-3/4 on state change.
- Status page — update on SEV-1 / SEV-2; on by default unless the user opts out with a stated reason.
- Stakeholder list — who hears each update (eng-lead, PO, support, leadership). Pre-decide so updates are not rewritten per-recipient.
3. Hold the timeline
Append-only log: timestamp + actor + observation. No edits, no "actually it was earlier" — corrections are new entries. Drives the post-mortem and prevents memory rewrite.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 156 lines · 48 tokens per session scan A 8a5ba02dd214
incident-commander is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 1,435 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-09-03.
Other skills, from other repositories
save-progress
Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to .claude/project-task-state.json so next session can load it via…
meta-theory
MetaKim executable governance dispatcher. It classifies the run, loads only needed references, preserves foundational capabilities and runtime-native abilities, routes owner + weapon + dependency + runtime + OS + verification, and closes only with evidence, intent acceptance, and writeback decision.
same-set-reusable-flow-for-project-file-inventor
Reusable MetaKim file inventory classification flow. It helps separate durable sources, generated evidence, runtime mirrors, temporary state, and risky unknowns before cleanup or commit.
starreel-drama-production
Operating skill for any AI agent driving the StarReel short-drama production pipeline (script → rewrite → extract → portraits + sheets → storyboards → frames → video → voiceover → final cut) over MCP or REST. Covers the ordered workflow, the entry-point decision table (which channel each kind of customer material…
seedance-20
Generate and direct cinematic AI videos with Seedance 2.0 (ByteDance/Dreamina/Jimeng). Covers text-to-video, image-to-video, video-to-video, and reference-to-video workflows with @Tag asset references, multi-character scenes, audio design, and post-processing. Use when making AI video, writing Seedance prompts…
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.