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-jev-failure-triagegit 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-jev-failure-triage)<a href="https://agentmods.dev/skills/rlaope/oh-my-hermes/omh-jev-failure-triage"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-jev-failure-triage/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-jev-failure-triage"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-jev-failure-triage.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.00077 | $0.00696 |
| Opus 5.5 | $0.00031 | $0.00278 |
| Sonnet 5.5 | $0.00015 | $0.00139 |
| Haiku 4.5 | $0.00008 | $0.00070 |
Grade A, and why
omh-jev-failure-triage 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jev Failure Triage
Required: the failing command, an error excerpt, and the retry count. Output: failure_triage/v1 next move with its rule.
Read skill_view(name='omh-routing', file_path='references/jev-rail.md') before the first ask: consent, what leaves the machine, limits, and non-answer statuses. Prepared OMH routing is not execution or approval. Shared product, routing, compatibility, and evidence rules: skill_view(name='omh-routing', file_path='references/skill-common-rail.md').
Contract: references/full-contract.md. Preset: references/preset.md.
Procedure
- Name what leaves the machine: the command and an error excerpt (plus earlier attempt excerpts when repeating).
- Call
omh_jev_askwithpreset: failure_triage/v1,state{error_excerpt, last_command, earlier_attempts}, andattempts_so_far. - Report
policy_result.outcomeand its rule beside the raw answers. - Hand the fix to
build-failure-triageoragent-debug; a rerun still needs the host's approval.
Completion Checklist
- Preserve workflow intent and stop conditions; load the full contract before claiming completion.
- Reply in the user's own words and the host's own voice: its SOUL.md persona owns reply language, tone, speech level, and sentence endings, progress updates included (where it sets no language, use the one the user wrote in), and OMH shapes structure and content only; OMH's record terms (surface, lane, wrapper, handoff, evidence boundary, not_observed) stay in records and tool calls, never in the sentence the user reads unless they ask about one; and when a stop condition or a decision the user owns ends the turn, offer the next action as a question rather than declaring what will not be done.
- Report the tool's status, ask_id, served model, and cost source; a non-answer is
not_observedwithrule: not_answered:<status>, never Jev's answer. - Record observed delegation results; use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.
What ships with it
2 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.
- 3d ago Changed · +3 lines 50182e422a0b
- 16d ago Changed 0ba215173203
- 21d ago Changed · +12 tokens per session b59495a355d1
- 23d ago First seen · 43 lines · 65 tokens per session scan A e8f3251ab57c
omh-jev-failure-triage is a skill published in the GitHub repository rlaope/oh-my-hermes (3,392 stars, last pushed today), licensed MIT. It adds 77 tokens to every session and 696 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-24.
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.