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-backendgit 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-backend)<a href="https://agentmods.dev/skills/rlaope/oh-my-hermes/omh-backend"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-backend/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-backend"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-backend.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.00075 | $0.02366 |
| Opus 5.5 | $0.00030 | $0.00946 |
| Sonnet 5.5 | $0.00015 | $0.00473 |
| Haiku 4.5 | $0.00007 | $0.00237 |
Grade A, and why
omh-backend 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 yesterday.
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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend
This is an OMH backend workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
Why This Exists
backend gives OMH a first-class server-side workflow so Hermes can prepare auth boundaries, error paths, response shapes, and migration order without becoming the hidden runtime that executes them.
Do Not Use When
- The work is the database itself -- a slow query and the index that fixes it, DDL that locks a live table, N+1 queries, or when to partition or shard; use
omh-relational-db, which owns the lock behaviour and rollback of each statement. - The request is about web UI, layout, or a design system; use
omh-frontend. - The request is a security posture or threat review rather than a service design; use
omh-security-safety-review. - The request is to run or judge the verification of an already-built service; use
omh-verification-gate. - The request is a Rust-language change whose risk is compiler, ownership, or
unsafediscipline; useomh-rust. - The work is a batch or streaming job's rerun, backfill, duplicate rows, or a warehouse table's downstream readers; use
omh-data-pipelines.
Examples
Good example:
- Prompt: Design a REST API with a Postgres schema and migrations for the billing service.
- Expected behavior: Prepare backend_service_contract/v1, auth_boundary_map/v1, error_path_table/v1, response_shape_contract/v1, and schema_migration_plan/v1, then hand off with the per-stack reference named.
- Why: The request is server-side design across an endpoint surface and its storage, before any code exists.
Bad example:
- Prompt: The migration is written, so mark the schema as migrated and the API as live.
- Expected behavior: Mark migration application, integration runs, and deployment as not_observed and name the smallest observed proof for each.
- Why: A prepared migration plan is not an applied migration, and a contract is not a running service.
Completion Checklist
- The surface, its callers, and each caller's trust level are named.
- The auth_boundary_map/v1 states where trust changes and which check enforces it on every path.
- The error_path_table/v1 covers each failure mode with status, body shape, retryability, and redaction rule.
- The response_shape_contract/v1 is consistent across endpoints rather than per-endpoint improvisation.
- Storage changes carry an expand/backfill/switch/contract order with a rollback point per step.
- A change to an existing contract carries its consumer list or an explicit
consumers_not_enumerable, plus the compatibility window, migration path, and sunset date. - The handoff names the executor, the stack, and the per-stack reference to load first.
- Implementation, migrations, integration runs, and deployment stay observed-only.
What ships with it
3 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.
- yesterday Changed f956b8cbe9ef
- 3d ago Changed · +1 lines 818efca06022
- 4d ago Changed 20d4d6108b4d
- 6d ago Changed ef59bf728831
- 12d ago Changed · +1 lines 96b3ce8c4bd3
- 25d ago Changed · +3 lines 10441cdec74a
- 27d ago Changed · +1 lines 6a0e7be4fe87
- 28d ago Changed · +1 lines c12e6b0ed748
- 1mo ago Changed · +7 tokens per session 5d692b4c33ab
- 1mo ago First seen · 144 lines · 68 tokens per session scan A b8800e59de78
omh-backend is a skill published in the GitHub repository rlaope/oh-my-hermes (4,206 stars, last pushed today), licensed MIT. It adds 75 tokens to every session and 2,366 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
api-test-suite-builder
Generate API tests from routes and contracts for authentication, validation, pagination, errors, uploads, and limits in Node.js or Python projects.
api-design-reviewer
Use when reviewing API designs for consistency, usability, versioning, error semantics, security, backward compatibility, and developer experience before implementation or release.
lark-skill-maker
A guide for creating reusable coding-agent skills that call Lark APIs, which are the interfaces used to automate Lark actions.
nornweave-api
Give AI agents their own email inboxes using the NornWeave API. Use when building email agents, sending/receiving emails programmatically, managing inboxes, retrieving threads, searching messages, or integrating with email providers (Mailgun, SES, SendGrid, Resend). NornWeave provides LLM-ready markdown parsing and…
api-and-interface-design
Design REST/GraphQL APIs, module interfaces, and type contracts when creating endpoints or changing public boundaries.
mcp-builder
Build MCP servers that expose external APIs or services through well-scoped tools in Python or TypeScript.