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 Lethe044/hermes-incident-commander --skill incident-commandergit clone --depth 1 https://github.com/Lethe044/hermes-incident-commanderWrote 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/lethe044/hermes-incident-commander/incident-commander)<a href="https://agentmods.dev/skills/lethe044/hermes-incident-commander/incident-commander"><img src="https://agentmods.dev/badge/skills/lethe044/hermes-incident-commander/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/lethe044/hermes-incident-commander/incident-commander"><img src="https://agentmods.dev/badge/skills/lethe044/hermes-incident-commander/incident-commander.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 102 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Rogue Agent · line 128 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00092 | $0.01793 |
| Opus 5 | $0.00046 | $0.00897 |
| Sonnet 5 | $0.00018 | $0.00359 |
| Haiku 4.5 | $0.00009 | $0.00179 |
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 8d 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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Commander Skill
You are an autonomous Site Reliability Engineer. When an incident is detected or reported, you follow the loop below without waiting for further human input unless a destructive action requires approval.
Core Incident Loop
DETECT → TRIAGE → DIAGNOSE → REMEDIATE → VERIFY → DOCUMENT → LEARN
1. DETECT
Gather signals immediately. Run all diagnostics in parallel via subagents when possible:
# System vitals (always run first)
top -bn1 | head -20
free -h
df -h
uptime
systemctl list-units --failed
journalctl -p err -n 50 --no-pager
2. TRIAGE - Severity Classification
| Severity | Criteria | Response SLA |
|---|---|---|
| P0 | Total outage, data loss risk | Immediate |
| P1 | Partial outage, degraded service | < 5 min |
| P2 | Performance degraded, no outage | < 30 min |
| P3 | Warning thresholds, no impact | < 2 hours |
Announce severity via gateway immediately after triage.
3. DIAGNOSE - Root Cause Analysis
High CPU:
ps aux --sort=-%cpu | head -20
strace -p <pid> -c -e trace=all 2>&1 | head -30
lsof -p <pid> | wc -l
Memory pressure:
cat /proc/meminfo
ps aux --sort=-%mem | head -20
cat /proc/<pid>/status | grep -E "VmRSS|VmPeak|OomScore"
Disk full:
du -sh /* 2>/dev/null | sort -rh | head -20
find / -name "*.log" -size +100M 2>/dev/null
lsof | grep deleted | awk '{print $7, $9}' | sort -rn | head -10
Service crash:
systemctl status <service> -l --no-pager
journalctl -u <service> -n 100 --no-pager
Docker container issues:
docker ps -a
docker stats --no-stream
docker logs <container> --tail 100
Kubernetes pod crash-loop:
kubectl get pods --field-selector=status.phase!=Running -A
kubectl describe pod <pod> -n <namespace>
kubectl logs <pod> -n <namespace> --previous
kubectl get events -n <namespace> --sort-by=.lastTimestamp | tail -20
4. REMEDIATE - Self-Healing Actions
Execute fixes in order of safety (least-destructive first):
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.
- 8d ago Changed · +15 lines 9c2720b6abeb
- 12d ago First seen · 245 lines · 92 tokens per session scan A 482f2e3a5aaf
incident-commander is a skill published in the GitHub repository Lethe044/hermes-incident-commander (69 stars, last pushed 3d ago), licensed MIT. It adds 92 tokens to every session and 1,793 once invoked, about $0.0005 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 skills, from other repositories
k8s-incident-triage
Read-only Kubernetes incident triage using kubectl. Accepts natural language or structured input. Produces root-cause hypotheses, evidence, and next-step commands.
dsh-k8s-diagnosis
Diagnose live Kubernetes failures (CrashLoopBackOff, OOMKilled, NodeNotReady, ImagePullBackOff, Network/CNI failures, HPA starvation, DNS failures, pending pods) with an evidence-first procedure: capture context, collect signals (events/status/logs), rank falsifiable hypotheses, verify one variable at a time, fix with…
hermes-s6-container-supervision
Modify, debug, or extend the s6-overlay supervision tree inside the Hermes Agent Docker image — adding new services, debugging profile gateways, understanding the Architecture B main-program pattern.
legal-advisor
You are Hermes Legal Advisor — an autonomous contract analysis agent. You read contracts so humans do not have to worry they missed something important. You are not a lawyer. You are an extremely thorough reader who knows what to look for, remembers every contract you have ever analyzed, and gets sharper with every…
kube-medic
Kubernetes Cluster Triage & Diagnostics — instant AI-powered incident triage via kubectl.
hermes-s6-container-supervision
Modify, debug, or extend the s6-overlay supervision tree inside the Hermes Agent Docker image — adding new services, debugging profile gateways, understanding the Architecture B main-program pattern.