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-capability-togglegit 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-capability-toggle)<a href="https://agentmods.dev/skills/rlaope/oh-my-hermes/omh-capability-toggle"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-capability-toggle/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-capability-toggle"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-capability-toggle.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.01339 |
| Opus 5.5 | $0.00030 | $0.00536 |
| Sonnet 5.5 | $0.00015 | $0.00268 |
| Haiku 4.5 | $0.00008 | $0.00134 |
Grade A, and why
omh-capability-toggle 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 2d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Capability Toggle
This is a Hermes-native capability-toggle workflow skill.
Why This Exists
capability-toggle exists because OMH shipped one binary install lever -- 9 core skills or all of them -- so a user who wanted the coding surface but not the memory surface had to take both. It turns that into a per-family choice without uninstalling OMH.
Do Not Use When
- The user wants to run the workflow a family owns rather than change whether that family is offered.
- The user is asking to build an on/off switch inside their own product.
- The user wants OMH removed entirely, which is the uninstall path rather than a capability policy change.
- The user wants one skill hidden on one messaging platform or everywhere; that is Hermes' own hermes skills config, an interactive command the person runs in a terminal, and OMH writes no Hermes config.
Examples
Good example:
- Prompt: turn off memory, I already run my own memory system
- Expected behavior: Disable the retain_knowledge family, report the four memory workflows removed and the five core skills retained, and name the enable command.
- Why: The request is about which OMH surfaces are offered locally, not about capturing a memory.
Bad example:
- Prompt: add a dark mode toggle to my settings page
- Expected behavior: Route to frontend or coding delegation instead of capability policy.
- Why: That is a feature in the user's own product, not an OMH capability family.
Completion Checklist
- The affected family is named by its canonical id, not guessed from a partial word.
- Removed workflows and retained core skills are listed separately.
- The reversing command is stated so the change never reads as permanent.
- Locally modified skill files are reported as retained exceptions rather than deleted.
Recovery Notes
- If the family id is ambiguous, list all six and ask rather than picking the closest match.
- If a disable would remove a core skill, refuse that part and report it; core skills are the floor doctor checks for.
- If files were kept with --keep-files, say the policy changed but the files remain so the state is not misread as a full removal.
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.
- 2d ago Changed f214e05ae97a
- 10d ago Changed c5d9cb6236bc
- 11d ago Changed · +3 lines ba376ae3cdf9
- 24d ago Changed 90f8a45a6ca1
- 29d ago Changed · +4 tokens per session abe66f1c81a0
- 1mo ago Changed · +1 lines d92cf4f3c317
- 1mo ago Changed · -6 lines 6dfa8c76d976
- 1mo ago Changed 6e6cdd0b9fb5
- 1mo ago Changed 0e61755244bd
- 1mo ago First seen · 119 lines · 72 tokens per session scan A 2461ce9ae603
omh-capability-toggle is a skill published in the GitHub repository rlaope/oh-my-hermes (3,912 stars, last pushed today), licensed MIT. It adds 76 tokens to every session and 1,339 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
managing-mcp-servers
Use when the user asks to add, change, remove, enable or disable an MCP server, or when an MCP tool is missing, needs sign-in, fails, or was blocked. ThinkRail runs pi in-process, so there is no pi command to call.
novel-craft
A writing guide for planning and revising long-form Chinese web fiction. It covers story premises, outlines, characters, rules, scenes, reader expectations, pacing, continuity, and revision diagnosis.
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.
asking-user-questions
Use when composing an askuserquestion round inside a workflow, or when a workflow skill names it at a question step. Shared norms for the tool — not a workflow, nothing to execute.
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
story-long-analyze
A structured process for deeply analysing a long online novel, starting with its opening three chapters and continuing chapter by chapter.