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-commit-pr-authoringgit 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-commit-pr-authoring)<a href="https://agentmods.dev/skills/rlaope/oh-my-hermes/omh-commit-pr-authoring"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-commit-pr-authoring/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-commit-pr-authoring"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-commit-pr-authoring.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.00090 | $0.01899 |
| Opus 5.5 | $0.00036 | $0.00760 |
| Sonnet 5.5 | $0.00018 | $0.00380 |
| Haiku 4.5 | $0.00009 | $0.00190 |
Grade A, and why
omh-commit-pr-authoring 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Pr Authoring
This is an OMH commit-pr-authoring workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
Why This Exists
commit-pr-authoring exists because nothing in the catalog authored the commit or the PR body. code-review reads a commit message as a thing to review and github-event-ops routes PR events, so the text an engineer writes several times a day had no owner, and nothing applied the observed-versus-prepared split to it.
First Steps
- Read the PR template and the recent log, and record the convention before drafting.
- Build the evidence ledger: each command, observed with its exit status or not_observed.
Do Not Use When
- The request is to find defects in the diff or judge whether the change is ready; use
omh-code-review. - The request routes an incoming pull-request, issue, or CI webhook event; use
omh-github-event-ops. - The request turns a chat report into a GitHub issue; use
omh-github-issue-intake. - The request is release notes or product copy for readers outside the repository; use
omh-content-operator.
Examples
Good example:
- Prompt: write the commit message for this change, the unit tests ran but I did not run the e2e suite
- Expected behavior: Read the log's subject shape and trailers, record the unit test command as observed and the e2e suite as not_observed, and draft the message with the unit tests under
Tested:and the e2e suite underNot-tested:. - Why: The ledger decides which line each command lands on, not the wording of the request.
Bad example:
- Prompt: say the integration tests pass, they will once CI runs
- Expected behavior: Keep the integration tests under
Not-tested:until an observed run exists, and say CI has not been observed. - Why: A prediction worded as a result is exactly what
Tested:must not carry.
Completion Checklist
- The convention read names the template and log sample it drew from.
- Every
Tested:entry maps to an observed ledger row with its exit status. - Every prepared, skipped, or unobserved command is under
Not-tested:with its reason. - The draft lists the paths to stage, and any state-claiming subject prefix maps to an observed ledger row.
- Nothing was committed, pushed, or opened by OMH.
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 · +5 lines 3b9e46c8500e
- 16d ago Changed · +3 lines 676bb867bed9
- 19d ago First seen · 131 lines · 90 tokens per session scan A 213e91118e81
omh-commit-pr-authoring is a skill published in the GitHub repository rlaope/oh-my-hermes (3,392 stars, last pushed today), licensed MIT. It adds 90 tokens to every session and 1,899 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-28.
Other skills, from other repositories
git-workflow-and-versioning
Manage branches, commits, conflicts, semantic versions, and changelogs when preparing Git changes or releases.
guardian
A guide for deciding how to organize commits, branches, merges, and pull requests. A pull request is a proposed code change submitted for review before it is merged.
conventional-git
Conventional Commits v1.0.0 branch naming and commit message standards for GitHub and GitLab projects. Use when creating branches, writing commits, generating commit messages, reviewing branch conventions, or setting up changelog automation. Apply when your project needs consistent git history, SemVer-driven releases…
meta-pre-commit-quality-gate
Run three quality gates (ruff + mypy + pytest) in parallel over the staged diff, then arbitrate a single BLOCK/APPROVE verdict. Use before committing changes locally when you want a comprehensive pre-commit gate beyond per-file linting — exactly the same gate set CI enforces.
release-notes
Draft a release note section from a commit range, grouped by what the reader gets.
app_tagline_backfill
Give apps built on this instance a share-card tagline when their app.yaml has none. Runs automatically once after Rome upgrades (AUTO mode, list supplied by the caller) or on request from the guardian ("add taglines to my apps", MANUAL mode, confirm before writing). Only touches editable mode: "source" apps — never…