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.
Borrowing it
Nothing to install: this file belongs to rlaope/oh-my-hermes. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rlaope/oh-my-hermes/main/AGENTS.mdgit 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/instructions/rlaope/oh-my-hermes/agents-md)<a href="https://agentmods.dev/instructions/rlaope/oh-my-hermes/agents-md"><img src="https://agentmods.dev/badge/instructions/rlaope/oh-my-hermes/agents-md/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/instructions/rlaope/oh-my-hermes/agents-md"><img src="https://agentmods.dev/badge/instructions/rlaope/oh-my-hermes/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.03868 | $0.03868 |
| Opus 5 | $0.01934 | $0.01934 |
| Sonnet 5 | $0.00774 | $0.00774 |
| Haiku 4.5 | $0.00387 | $0.00387 |
Grade A, and why
oh-my-hermes AGENTS.md 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 — 342 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OMH Agent Contract
This file is the repo-local operating contract for coding agents working on oh-my-hermes, including Codex, Claude Code, Hermes runtime/handoff paths, and generic executor profiles.
Product Direction
Read docs/DIRECTION.md before changing architecture, workflow behavior,
wrapper contracts, generated skill guidance, or coding delegation semantics.
OMH is a Hermes-native wrapper orchestration layer. Keep Hermes responsible for chat intake, clarification, source-backed research, planning, and status narration. Keep main coding work delegated to the selected coding owner through explicit prepared handoffs and observed evidence. Do not make Codex the implicit default in product language, docs, schemas, prompts, or reports when Claude Code, Hermes runtime/handoff paths, or generic executor profiles are also valid owners.
When developing OMH itself, treat Codex, Claude Code, and Hermes runtime/handoff paths as first-class product surfaces. User-facing runtime selection may choose one coding owner for a task, but OMH feature design, contracts, docs, setup, memory recall, and status/reporting changes should consider all three surfaces unless a change is explicitly scoped to one executor. If support differs, document the difference as a capability boundary instead of silently optimizing for Codex.
Do not turn OMH into a hidden Hermes runtime patch, transport bot, network service, LLM router, or secret coding executor. The one sanctioned execution surface is the explicit opt-in fanout dispatch bridge described under Implementation Boundaries — operator-invoked, local-only, fully observed, never hidden and never a default.
Command Audience
Treat natural-language Hermes chat as the normal product surface. Most people
should only need to run omh setup, omh update, and omh doctor directly.
Removal or unusual repair commands are exceptional maintenance paths, not the
day-to-day OMH workflow.
Commands under omh chat, omh coding, omh runtime, omh memory, omh loop, omh goal, omh harness, omh capabilities, omh release, omh state, and similar control-plane groups primarily exist for Hermes Agent,
wrappers, coding agents, automations, and maintainers. Public docs may show
those commands as integration or operator references, but must label the
audience explicitly and must not make normal users memorize or run them to get
value. Describe the human action as an intent or outcome, such as asking Hermes
to prepare coding work, while keeping the backend command in the agent-facing
reference.
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 · +26 lines · +379 tokens per session 5a33ec4718a0
- 5d ago Changed · +22 lines · +320 tokens per session 829d9e27dfa1
- 9d ago First seen · 294 lines · 3,169 tokens per session scan A 0f559da65cf4
oh-my-hermes AGENTS.md is an instructions file published in the GitHub repository rlaope/oh-my-hermes (1,582 stars, last pushed today), licensed MIT. It adds 3,868 tokens to every session, about $0.0193 per session on Opus 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.