oh-my-hermes is an operating layer for Hermes Agent that organizes requests into workflows for planning, research, creation, coding handoffs, operations, and project memory. Hermes users run these workflows through the desktop app, CLI, or messenger app, while the catalogue add-ons extend its native capabilities.
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 rlaope/oh-my-hermes --skill omh-live-incident-responsegit clone --depth 1 https://github.com/rlaope/oh-my-hermesWrote 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/rlaope/oh-my-hermes/omh-live-incident-response)<a href="https://agentmods.dev/skills/rlaope/oh-my-hermes/omh-live-incident-response"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-live-incident-response/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/rlaope/oh-my-hermes/omh-live-incident-response"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-live-incident-response.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.02170 |
| Opus 5.5 | $0.00035 | $0.00868 |
| Sonnet 5.5 | $0.00017 | $0.00434 |
| Haiku 4.5 | $0.00009 | $0.00217 |
Grade A, and why
omh-live-incident-response 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.
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Live Incident Response
This is an OMH live-incident-response workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
Why This Exists
live-incident-response exists because an incident that is still open had no owner. support-operations sent an active incident to reliability-review, and reliability-review reviews incident notes after the fact, so the one skill that saw the request handed it to a postmortem while the outage was still running.
Do Not Use When
- The incident is over and the request is the postmortem, the SLO or error-budget consequence, or remediation follow-up; use
omh-reliability-review. - The request is one customer's support case needing a reply, a severity opinion, and an escalation path, with no incident declared; use
omh-support-operations. - The request is a release being rolled out and watched -- deploy checklist, health signals, rollback criteria -- and nothing has been declared broken; use
omh-deploy-and-monitor. - The request is to send the page, publish the status-page update, or deliver the customer notice; use
omh-apps, which records a send as observed only on a returned result. - The request asks whether a release is ready across rollout, rollback, and observability, before anything broke; use
omh-production-audit.
Examples
Good example:
- Prompt: we have a production outage right now, declare severity and assign an incident commander
- Expected behavior: Prepare live_incident_record/v1: ask for the user-visible symptom and blast radius, declare the severity with the observation that set it, name the commander and the remaining roles, open the append-only timeline, and state which signal decides recovery.
- Why: The incident is open, so severity and command are live state rather than findings to review later.
Bad example:
- Prompt: live-incident-response write up the postmortem for last week's outage and what it cost the error budget
- Expected behavior: Route to
reliability-review: a closed incident is reviewed, never commanded. - Why: Severity, roles, and a running timeline have no subject once the incident is over.
What ships with it
1 file 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.
- 3d ago Changed · +1 lines b757b8770d0e
- 16d ago Changed · +3 lines 6b82f165b715
- 21d ago Changed · +4 tokens per session f32bd8882750
- 23d ago Changed · +6 lines 96542b38eba9
- 27d ago Changed dd2ca3ab1f61
- 1mo ago First seen · 136 lines · 83 tokens per session scan A 60e970360499
omh-live-incident-response is a skill published in the GitHub repository rlaope/oh-my-hermes (3,392 stars, last pushed today), licensed MIT. It adds 87 tokens to every session and 2,170 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-09-16.
Other skills, from other repositories
azure-diagnostics
Investigate AKS, VM, App Service, Functions and messaging incidents using scoped evidence.
kubernetes-specialist
Use when managing Kubernetes clusters, debugging Pods and workloads, designing Helm charts, reviewing manifests, or improving deployment, scaling, and observability practices.
python-performance
Profile and optimize Python code using cProfile, memory profilers, and performance best practices. Use when debugging slow Python code, optimizing bottlenecks, or improving application performance.
cloudflare-troubleshooting
Diagnose Cloudflare DNS, TLS, redirects, and configuration issues using live API settings and request evidence.
doubt-driven-development
Review high-risk or uncertain engineering decisions adversarially when independent verification can expose costly assumptions before implementation.
debugging-and-error-recovery
Diagnose failing tests, broken builds, and unexpected runtime behavior through reproduction, evidence, root-cause analysis, and focused recovery.