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-deliverable-packagegit 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-deliverable-package)<a href="https://agentmods.dev/skills/rlaope/oh-my-hermes/omh-deliverable-package"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-deliverable-package/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-deliverable-package"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-deliverable-package.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.00085 | $0.01688 |
| Opus 5.5 | $0.00034 | $0.00675 |
| Sonnet 5.5 | $0.00017 | $0.00338 |
| Haiku 4.5 | $0.00009 | $0.00169 |
Grade A, and why
omh-deliverable-package 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deliverable Package
This is an OMH deliverable-package workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
Why This Exists
deliverable-package exists because a requested file moves through prepared, generated, QA-checked, approved, and attached states that no single tool reports together: it tracks each file through them and reports a state only from that state's own evidence, never from an earlier one's.
Do Not Use When
- Planning a deck, PDF, workbook, or document from source inputs before any file exists (its outline, target formats, and QA ladder); use
omh-materials-package. - A text-only report, executive brief, or slide outline with no file to produce; use
omh-report-package.
Examples
Good example:
- Prompt: deliverable-package turn this research into PPT and PDF with attachment status.
- Expected behavior: Produce
prepare_deliverable_packagewith required context, wrapper actions, and not-evidence boundaries. - Why: The prompt names a real workflow surface that Hermes can orchestrate without hiding execution.
Bad example:
- Prompt: deliverable-package claim the PDF was attached without observed file evidence.
- Expected behavior: Report the missing observed evidence or authority instead of claiming the external step happened.
- Why: Prepared OMH guidance is not platform, runtime, connector, file, memory, or delivery evidence.
Completion Checklist
- The deliverable type, audience, source inputs, QA ladder, and delivery boundary are named.
- Prepared generation, generated file, render QA, approval, attachment, and delivery are separate states.
- The next action says whether to generate, revise, QA, approve, attach, or deliver.
Recovery Notes
- If generation tooling is missing, prepare a prompt or package handoff and mark file output not_observed.
- If QA or attachment evidence is missing, keep generated/delivered states separate and show the next check.
When to Use
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 · +4 lines · +4 tokens per session d73265970c75
- 5d ago Changed · +1 lines 3180218e2f12
- 14d ago Changed · +3 lines 065ab9406804
- 27d ago Changed · +3 lines 2bfc4e81fe85
- 1mo ago Changed · +1 tokens per session d95127680f84
- 1mo ago Changed · +6 lines 814984ab322d
- 1mo ago Changed · -11 lines 7f3305d7e2a3
- 1mo ago Changed 97e00a709f22
- 1mo ago Changed 3dded57bac8e
- 1mo ago First seen · 120 lines · 80 tokens per session scan A eb072fdc7bca
omh-deliverable-package is a skill published in the GitHub repository rlaope/oh-my-hermes (4,366 stars, last pushed today), licensed MIT. It adds 85 tokens to every session and 1,688 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
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.
lark-workflow-standup-report
A workflow that combines calendar events with unfinished Lark tasks to produce a daily or weekly work summary.
notion-knowledge-capture
Convert conversations and notes into structured, linkable Notion pages for easy reuse.
obsidian
Use when reading, searching, creating, or editing notes in an authorized Obsidian vault while preserving frontmatter, wikilinks, and unrelated notes.
docs-cleaner
Consolidate overlapping documentation and remove repetition while preserving useful content, references, and ownership.
lark-contact
A Feishu (Lark) contacts tool for finding users or bots and looking up their profiles and contact details.