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-memory-syncgit 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-memory-sync)<a href="https://agentmods.dev/skills/rlaope/oh-my-hermes/omh-memory-sync"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-memory-sync/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-memory-sync"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-memory-sync.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.00096 | $0.04168 |
| Opus 5.5 | $0.00038 | $0.01667 |
| Sonnet 5.5 | $0.00019 | $0.00834 |
| Haiku 4.5 | $0.00010 | $0.00417 |
Grade A, and why
omh-memory-sync 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Sync
This is a Hermes-native memory-sync workflow skill.
Why This Exists
memory-sync exists because Hermes' memory files are small, capped, and written by more than one hand -- the model, Hermes' own background review, and the person -- so a stale or wrong entry rides in every prompt until someone checks it: this review walks the entries with the person one claim at a time, prepares one diff they approve, and reports only the write Hermes itself returns.
Do Not Use When
- The user states a new fact to remember; capture it with
omh-memory-new. - The user asks what was decided or rejected before; use
omh-decision-recall. - The user wants a memory provider enabled, switched, paused, or removed; use
omh-external-connector-readiness, which owns the provider slot.
Examples
Good example:
- Prompt: memory-sync inspect stale MEMORY.md claims, prepare a native write diff, and ask which claims to keep, revise, or archive.
- Expected behavior: Produce
prepare_memory_syncwith required context, wrapper actions, and not-evidence boundaries. - Why: The prompt names a real workflow surface that Hermes can orchestrate without hiding execution.
Bad example:
- Prompt: memory-sync claim a prepared native diff changed MEMORY.md or USER.md.
- Expected behavior: Report the missing observed evidence or authority instead of claiming the external step happened.
- Why: Prepared OMH guidance is not platform, runtime, connector, file, memory, or delivery evidence.
Completion Checklist
- Confirm the workflow target, evidence boundary, and stop condition are named.
- Report which outputs are prepared, observed, blocked, or missing.
- Name the smallest next verification or handoff instead of claiming completion from narration.
Recovery Notes
- If required context is missing, ask one blocking question or route back to the narrower workflow.
- If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.
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.
- 3d ago Changed 1bce90d7adaa
- 12d ago Changed · +5 lines a9ae9aa55b15
- 19d ago Changed · +1 lines 222740808154
- 25d ago Changed cb56ab0d2485
- 1mo ago Changed · +8 tokens per session ada7e11ea0bf
- 1mo ago Changed · +1 lines ee163a52da36
- 1mo ago Changed · +1 lines 2a28f9d8cf3a
- 1mo ago Changed · +12 lines 396053e94ca5
- 1mo ago Changed · +1 lines 9ab02961c9d9
- 1mo ago First seen · 156 lines · 88 tokens per session scan A cf07016f4ff7
omh-memory-sync is a skill published in the GitHub repository rlaope/oh-my-hermes (4,206 stars, last pushed today), licensed MIT. It adds 96 tokens to every session and 4,168 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
add-new-entry-from-temp-md
Format new entries from temp.md into tempentries.md, ready to insert into the section files. USE FOR: adding new resources to the knowledge base. DO NOT USE FOR: editing existing entries or restructuring sections.
context-engineering
Diagnose missing or overloaded agent context and configure project instructions when setup or context quality is the task.
experience-manager
A project knowledge system for recording, finding, reviewing, and improving lessons learned. It stores rules, working strategies, technical knowledge, and past history at different levels.
honcho
Configure and troubleshoot Honcho memory for Hermes.
lore
Curating cross-agent knowledge and institutional memory: extracts patterns from agent journals into METAPATTERNS.md, detects knowledge decay, propagates best practices. Use for memory curation.
cast
A system for creating and managing personas, which are defined characters or user profiles used by agents. It supports registering, updating, checking, sharing, and giving these personas a consistent voice.