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-refactor-plangit 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-refactor-plan)<a href="https://agentmods.dev/skills/rlaope/oh-my-hermes/omh-refactor-plan"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-refactor-plan/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-refactor-plan"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-refactor-plan.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.00100 | $0.01889 |
| Opus 5.5 | $0.00040 | $0.00756 |
| Sonnet 5.5 | $0.00020 | $0.00378 |
| Haiku 4.5 | $0.00010 | $0.00189 |
Grade A, and why
omh-refactor-plan 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactor Plan
This is an OMH refactor-plan workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
Why This Exists
refactor-plan exists because boundary-changing refactors bounced between goal planning and behavior-preserving cleanup with neither owning the execution shape: the phase order, the per-phase rollback, and the files table that make a large refactor reviewable and abortable.
Do Not Use When
- The refactor's direction is still contested or the goal itself needs consensus planning; use
ulw-plan. - The work is deletion-first cleanup with no boundary changes; use
omh-ai-slop-cleaner. - The plan is done and the claim is that work is complete; use
omh-verification-gatefor the evidence close. - The version bump carries a security advisory, a CVE, or a leaked secret; use
omh-security-event-response, which owns containment and closure.
Examples
Good example:
- Prompt: We decided to split the billing module out of orders - plan the refactor so each step is shippable.
- Expected behavior: Map affected files and consumers from the import graph, name hidden coupling and blast radius, order the five phases with per-phase verification and rollback, ship the files table, and stop at the approval gate.
- Why: The direction is decided and the need is a phased, abortable execution shape - exactly this workflow's territory.
Bad example:
- Prompt: Should we even split billing out of orders?
- Expected behavior: Route to
ralplan: the direction is not decided, so consensus planning comes before phase planning. - Why: A phase plan for a contested direction launders a decision through logistics.
Completion Checklist
- Reconnaissance names affected files, boundaries, coupling, and blast radius from observed evidence.
- Every phase carries its verification command and its rollback point, and ends at a shippable commit.
- The files table covers every touched file with action, phase, and dependencies.
- For an upgrade, every breaking change row names its call sites or an observed empty search, and every stage names its rollback.
- The plan stopped at the approval gate; no implementation began without the user's go.
What ships with it
2 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.
- today Changed 68caead9ec75
- 5d ago Changed · +1 lines 979d895a63b7
- 14d ago Changed · +1 lines 4bf1cc9fc1ef
- 27d ago Changed · +3 lines fb2c648d8497
- 29d ago Changed · +4 lines dacc866c8439
- 1mo ago Changed · +7 tokens per session 84fac6c63c1d
- 1mo ago Changed · +6 lines 2488255f6aa6
- 1mo ago Changed · +1 lines d14d24391366
- 1mo ago Changed · -11 lines 96c77a0d51a3
- 1mo ago First seen · 126 lines · 93 tokens per session scan A 78f810bf2c44
omh-refactor-plan is a skill published in the GitHub repository rlaope/oh-my-hermes (4,366 stars, last pushed today), licensed MIT. It adds 100 tokens to every session and 1,889 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
nlpm-audit
Audit SKILL.md, AGENTS.md, prompts, hooks, and plugin manifests for instruction conflicts, quality, broken references, and manifest-to-disk drift.
api-design-reviewer
Use when reviewing API designs for consistency, usability, versioning, error semantics, security, backward compatibility, and developer experience before implementation or release.
pr-review-expert
Review GitHub PRs or GitLab MRs for correctness, security, compatibility, and affected test coverage, with actionable evidence tied to the diff.
improve-codebase-architecture
Review module boundaries, interface depth and high-leverage refactors with evidence.
gh-address-comments
Use when addressing GitHub PR review comments or issue comments on the current branch with gh CLI, including auth checks, comment triage, edits, verification, and replies.
doubt-driven-development
Review high-risk or uncertain engineering decisions adversarially when independent verification can expose costly assumptions before implementation.