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-buzzgit 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-buzz)<a href="https://agentmods.dev/skills/rlaope/oh-my-hermes/omh-buzz"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-buzz/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-buzz"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-buzz.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.00095 | $0.01521 |
| Opus 5 | $0.00048 | $0.00760 |
| Sonnet 5 | $0.00019 | $0.00304 |
| Haiku 4.5 | $0.00010 | $0.00152 |
Grade A, and why
omh-buzz 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 6d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Buzz
This is a Hermes-native buzz workflow skill.
Why This Exists
Hermes already owns the Buzz transport, but users need one discoverable OMH entry point that safely selects setup, attachment, or self-host operations and reports only the evidence actually observed.
Do Not Use When
- The user wants a Buzz-managed ACP runtime rather than Hermes' native Buzz gateway.
- The request is general media editing with no Buzz delivery target.
- The request is generic Docker or Nostr advice unrelated to a Buzz relay.
- The user is only asking whether OMH supports Buzz, with no request to run the workflow.
Examples
Good example:
- Prompt: Connect this Hermes gateway to my Buzz community and verify one inbound and outbound message.
- Expected behavior: Load the setup reference, collect the relay and membership inputs without exposing the private key, use Hermes' guided gateway setup, then report each observed verification stage.
- Why: The request names the native gateway task and an observable end-to-end stop condition.
Bad example:
- Prompt: Write a generic Nostr relay from scratch for OMH.
- Expected behavior: Route to planning or coding rather than presenting that transport as part of omh-buzz.
- Why: OMH reuses Hermes' native Buzz adapter and does not own a second Nostr transport.
Completion Checklist
- Exactly one of setup, media, or self-host is selected from request meaning; no internal lane is public.
- Secrets remain out of argv, logs, rendered output, and workflow artifacts.
- Configuration, process, relay, event acceptance, subscription, and client rendering are separate claims.
- Any state-changing self-host command remains user-driven and has an explicit rollback or backup boundary.
- The final answer names what was observed, what remains unobserved, and the next smallest proof action.
Recovery Notes
- If the Buzz CLI is missing, stop at installation guidance and do not claim gateway readiness.
- If relay authentication fails, separate membership, identity, and NIP-42 evidence before changing config.
- If a send receipt is malformed or lacks an event id, report ambiguous delivery and do not auto-retry.
- If self-host readiness is green but media fails, inspect MinIO and disk separately from relay readiness.
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.
- 6d ago Changed a7eeafc5a0be
- 11d ago First seen · 149 lines · 95 tokens per session scan A 532d80d92e93
omh-buzz is a skill published in the GitHub repository rlaope/oh-my-hermes (1,648 stars, last pushed today), licensed MIT. It adds 95 tokens to every session and 1,521 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
story-review
A review process for finding problems in a novel’s structure, characters, wording, and world rules. It can use several reviewers or one reviewer when others are unavailable.
story-long-analyze
A structured process for deeply analysing a long online novel, starting with its opening three chapters and continuing chapter by chapter.
moxiangtongxiu-perspective
A Chinese-language creative-writing guide built around character-led stories, interwoven plotlines, memorable dialogue, ensemble casts, and emotional contrasts. It is presented as a perspective associated with the author Mo Xiang Tong Xiu.
tiancantudou-perspective
A creative-writing guide based on the storytelling patterns associated with Chinese web novelist Tiancan Tudou. It focuses on stories where an underestimated character grows stronger through challenges and moves into new settings.
tianya-gods-team
A decision-making system in which 20 fictional specialist viewpoints analyze one question in parallel before a coordinating AI combines them. It covers areas such as history, economics, relationships, technology, mysteries, and culture.
lijigang-skill
A Chinese-language approach to writing precise, highly structured prompts, sometimes using Lisp-like notation. It combines concise wording, philosophical questioning, and a process for defining roles, conditions, output formats, and revisions.