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-automation-blueprintgit 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-automation-blueprint)<a href="https://agentmods.dev/skills/rlaope/oh-my-hermes/omh-automation-blueprint"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-automation-blueprint/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-automation-blueprint"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-automation-blueprint.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.00076 | $0.02538 |
| Opus 5.5 | $0.00030 | $0.01015 |
| Sonnet 5.5 | $0.00015 | $0.00508 |
| Haiku 4.5 | $0.00008 | $0.00254 |
Grade A, and why
omh-automation-blueprint 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automation Blueprint
This is a Hermes-native automation-blueprint workflow skill.
Why This Exists
automation-blueprint exists so a recurring request reaches Hermes' own Automation Blueprints and cron with the decisions they leave open (overlap, missed run, retry, backfill, failure pause, silence) settled first, without OMH becoming a hidden cron runner, transport bot, source retriever, or executor.
Do Not Use When
- An undecided lifecycle journey or growth experiment needs audience, consent, and measurement design before any schedule; use
omh-lifecycle-growthfirst. - The user needs a one-off report or deck; use
omh-report-packageoromh-materials-package. - The user asks to review incident metrics once; use
omh-reliability-review. - The user needs actual code changes; prepare a selected executor/runtime handoff after the blueprint or plan is accepted.
- The person is inside Hermes' own /blueprint setup for one of its catalog automations; answer the questions that flow asks and let it create the job instead of preparing a second blueprint.
- The recurring job would move money -- a purchase, a renewal, a top-up, or a transfer; use
omh-spend-gate, because an agent run on a schedule never spends, and a no-agent script that pays is a spend set up now: its card, typed yes, and cap come before the job exists.
Examples
Good example:
- Prompt: automation-blueprint every weekday run an uptime check and send a Slack digest only if status changes.
- Expected behavior: Draft prepared_native_blueprint/v1 with schedule intent, Slack delivery, a
[SILENT]reply for unchanged runs, research/report skills, missing evidence, and the next confirmation. - Why: The request is recurring, delivery-shaped, and must stay prepared until host automation and gateway delivery are observed.
Bad example:
- Prompt: automation-blueprint prove the Slack digest was delivered this morning.
- Expected behavior: Ask for observed Hermes/gateway delivery evidence or report the delivery as not_observed instead of claiming it happened.
- Why: A blueprint can prepare the scheduled operation, but it cannot prove runtime execution or delivery.
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.
- today Changed f29645e8e65e
- 5d ago Changed 3a3681cf28a4
- 6d ago Changed e0b1fcd2f8de
- 8d ago Changed 7be67cbb652e
- 13d ago Changed · +1 lines 4bcd6f3686b4
- 14d ago Changed · +8 lines 80aee44baf87
- 27d ago Changed c08b7f1c49b8
- 1mo ago Changed · +6 tokens per session cf9224dba265
- 1mo ago Changed · +1 tokens per session 964d60de56fc
- 1mo ago First seen · 133 lines · 69 tokens per session scan A 8a6a81ef7350
omh-automation-blueprint is a skill published in the GitHub repository rlaope/oh-my-hermes (4,366 stars, last pushed today), licensed MIT. It adds 76 tokens to every session and 2,538 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
todos
Use when the user asks for a shared plan, a task needs at least three substantive execution steps, or a loose TODO is pending. Without an explicit plan request, not for one-shot answers or checks, or one- to two-step work that is not already in the list.
lark-workflow-standup-report
A workflow that combines calendar events with unfinished Lark tasks to produce a daily or weekly work summary.
notion-knowledge-capture
Convert conversations and notes into structured, linkable Notion pages for easy reuse.
obsidian
Use when reading, searching, creating, or editing notes in an authorized Obsidian vault while preserving frontmatter, wikilinks, and unrelated notes.
docs-cleaner
Consolidate overlapping documentation and remove repetition while preserving useful content, references, and ownership.
lark-contact
A Feishu (Lark) contacts tool for finding users or bots and looking up their profiles and contact details.