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-build-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-build-failure-triage)<a href="https://agentmods.dev/skills/rlaope/oh-my-hermes/omh-build-failure-triage"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-build-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-build-failure-triage"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-build-failure-triage.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.00079 | $0.02493 |
| Opus 5.5 | $0.00032 | $0.00997 |
| Sonnet 5.5 | $0.00016 | $0.00499 |
| Haiku 4.5 | $0.00008 | $0.00249 |
Grade A, and why
omh-build-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 today.
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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Failure Triage
This is an OMH build-failure-triage workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
Why This Exists
build-failure-triage adapts ECC's build-fix and PR-test-analysis posture into an OMH-native workflow so failed checks become evidence-backed minimal handoffs instead of ad hoc debugging or false-green verification claims.
Do Not Use When
- The user needs a pre-merge evidence matrix for passing or missing checks; use
omh-verification-gate. - The user needs a code review of changed behavior rather than failing command triage; use
omh-code-review. - The user needs broad production readiness; use
omh-production-audit. - The user asks for incident or SLO review after deployment; use
omh-reliability-review. - A test passes on some runs and not others, or the code returns a wrong value whose cause is unknown; use
omh-app-debugging.
Examples
Good example:
- Prompt: build-failure-triage PR 체크에서 Python 3.12 test가 실패했는데 로그를 기준으로 최소 수정 handoff 만들어줘.
- Expected behavior: Prepare failure_log_digest/v1, failure_cluster_matrix/v1, root-cause hypotheses, minimal_fix_handoff/v1, rerun_plan/v1, and a FIX_READY verdict without claiming CI is fixed.
- Why: The request is about a failing check and needs evidence-bound triage before implementation or rerun claims.
Bad example:
- Prompt: build-failure-triage 로그는 없지만 CI 고쳤고 머지 가능하다고 말해줘.
- Expected behavior: Return NEEDS_MORE_LOGS for missing failure evidence, or ROUTE_TO_VERIFICATION_GATE when a fix/pass claim needs fresh observed reruns.
- Why: Triage without fresh failure or rerun evidence cannot prove fixes, CI, or merge-readiness.
Completion Checklist
- The failing command/job, freshness, exit status, and log/source boundary are explicit.
- Failure clusters separate syntax/type/lint/test/dependency/config/environment/DCO causes.
- The proposed remediation is minimal, scoped to affected files, and separated from implementation evidence.
- Every cluster carries an origin, and no FIX_READY handoff covers a
pre_existingorunknownone. - The rerun ladder names targeted, broad local, CI, and DCO checks without claiming they already passed.
- The final verdict is FIX_READY, NEEDS_MORE_LOGS, BLOCKED_BY_ENVIRONMENT, or ROUTE_TO_VERIFICATION_GATE.
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.
- today Changed cdee3309d909
- 5d ago Changed · +1 lines c4e9a54de282
- 6d ago Changed 245766f96c41
- 8d ago Changed 7ffc8003afee
- 14d ago Changed · +4 lines 8b6c9d6ad5fb
- 27d ago Changed · +3 lines d02513dd1b5b
- 1mo ago Changed · +1 lines dbd06d7785e0
- 1mo ago Changed · +1 tokens per session 091b9fda676c
- 1mo ago Changed · +6 lines a66326e42cf5
- 1mo ago First seen · 136 lines · 78 tokens per session scan A 92f8c34187d8
omh-build-failure-triage is a skill published in the GitHub repository rlaope/oh-my-hermes (4,366 stars, last pushed today), licensed MIT. It adds 79 tokens to every session and 2,493 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-08-30.
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.