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-morning-briefgit 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-morning-brief)<a href="https://agentmods.dev/skills/rlaope/oh-my-hermes/omh-morning-brief"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-morning-brief/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-morning-brief"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-morning-brief.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.00098 | $0.01892 |
| Opus 5.5 | $0.00039 | $0.00757 |
| Sonnet 5.5 | $0.00020 | $0.00378 |
| Haiku 4.5 | $0.00010 | $0.00189 |
Grade A, and why
omh-morning-brief 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 4d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Morning Brief
This is a Hermes-native morning-brief workflow skill.
Why This Exists
morning-brief exists to connect mail and calendar access for an on-demand brief while keeping the connection strictly read and draft-only and credential entry outside chat, with explicit storage authorization.
Do Not Use When
- The user wants Hermes to check their email or calendar right now rather than set up the connection.
- The connection is already configured and the user only wants today's brief, not a setup walkthrough.
- The request needs a repository code change rather than a local MCP config edit.
Examples
Good example:
- Prompt: connect my email for a morning brief — I want a daily summary of mail and calendar.
- Expected behavior: Check the MCP prerequisite, diagnose the current connection, guide OAuth/token issuance, show the read/draft-only diff, and apply only after approval.
- Why: The request is a mail/calendar integration setup and needs the shared setup contract plus the Send-permission guardrail.
Bad example:
- Prompt: morning-brief: check my email for anything urgent.
- Expected behavior: Route to a mail-reading task instead of starting a connection setup walkthrough.
- Why: A one-off email check is a task request, not an integration setup request.
Completion Checklist
- If a prerequisite is unmet, mark that item "not applicable" and continue with the rest of the guide instead of blocking or guessing.
- Success is applicable-only: verification passes when every applicable item is confirmed complete, not when every possible item exists.
- The connection is confirmed read and draft-only, with Send permission never enabled, before the brief is reported ready.
Recovery Notes
- If the mail or calendar prerequisite is unmet, mark that surface "not applicable" and offer the brief scoped to whichever surface is connected.
- If authentication fails, guide reauthorization or reissuance through secure entry or user-side setup; do not request the failed credential in chat or silently retry it.
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.
- 4d ago Changed 72e2eff2a531
- 12d ago Changed f97148e03ffc
- 13d ago Changed · +4 lines ee4fdd3523c7
- 26d ago Changed 6f1b4f5ae68e
- 1mo ago Changed · +6 tokens per session 3eedaa3c0e0d
- 1mo ago Changed c84435deb786
- 1mo ago Changed · +1 lines fbf06ae3b7eb
- 1mo ago Changed cca7284d251e
- 1mo ago Changed fba7010ab711
- 1mo ago First seen · 122 lines · 92 tokens per session scan A 0df6f31c8798
omh-morning-brief is a skill published in the GitHub repository rlaope/oh-my-hermes (4,314 stars, last pushed today), licensed MIT. It adds 98 tokens to every session and 1,892 once invoked, about $0.0004 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-03.
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.