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-research-departmentgit 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-research-department)<a href="https://agentmods.dev/skills/rlaope/oh-my-hermes/omh-research-department"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-research-department/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-research-department"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-research-department.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.00096 | $0.02226 |
| Opus 5.5 | $0.00038 | $0.00890 |
| Sonnet 5.5 | $0.00019 | $0.00445 |
| Haiku 4.5 | $0.00010 | $0.00223 |
Grade A, and why
omh-research-department 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Department
This is a Hermes-native research-department workflow skill.
Why This Exists
research-department exists so Hermes users can start complex research-ops patterns without manually designing profiles, cron, knowledge storage, synthesis tooling, and delivery glue, while OMH keeps every runtime claim observed-only.
Do Not Use When
- The user only needs a one-off current-source lookup; use
ulw-research. - The user only needs a one-off business synthesis; use
omh-research-brief. - The request is pure scheduling with no source collection or synthesis; use
omh-automation-blueprint. - The user asks for coding implementation; prepare a selected executor/runtime handoff after the research plan is accepted.
- The request is one news watch over named companies, or a scheduled run of a watch that already exists, with no knowledge store, synthesis tool, or briefing lanes to set up, and Hermes' bundled
competitor-news-monitorskill is available; load that skill. - The user wants a one-off paper search by topic, author, category, or paper id rather than a recurring paper review, and Hermes' bundled
arxivskill is available; load that skill.
Examples
Good example:
- Prompt: Set up a Scout, Analyst, and Briefer research flow for daily competitor and market changes.
- Expected behavior: Prepare research_department_plan/v1 with Scout/Analyst/Briefer lanes, source inbox buckets, briefing status, knowledge-store and synthesis-tool readiness, and observed-only evidence requirements.
- Why: The request is recurring, source-backed, and operational; a single research brief would miss the ongoing workflow/status boundary.
Bad example:
- Prompt: research-department prove the synthesis tool queried the knowledge base and posted the Slack brief.
- Expected behavior: Ask for observed synthesis-tool and gateway delivery evidence or mark those states as not_observed.
- Why: The workflow pack can prepare the operating pattern, but it cannot prove external tool execution or delivery.
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 83e08bc4383b
- 4d ago Changed · +4 lines 7e5f057305fe
- 13d ago Changed · +11 lines d1ed83a65e79
- 26d ago Changed c065f17bfb8d
- 28d ago Changed 9f784d431216
- 1mo ago Changed · +7 tokens per session 343d43cc1e56
- 1mo ago Changed · +1 lines 6b48168a6461
- 1mo ago Changed 6576976d24b3
- 1mo ago Changed 7e3f676f6ed5
- 1mo ago First seen · 126 lines · 89 tokens per session scan A 67643a3c27f4
omh-research-department is a skill published in the GitHub repository rlaope/oh-my-hermes (4,314 stars, last pushed today), licensed MIT. It adds 96 tokens to every session and 2,226 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
starting-a-new-project
Use when the workspace is empty, has no code, and the user brings a raw project idea. Normally reached via setting-up-a-project; not for an existing project.
configuration
Use when a Project Agent reads or changes lore indexes and group memberships, managed presets, game modules, automations, Skills, or Agent profiles through configread and configapply.
interview-system-designer
Design hiring interviews, competency matrices, question banks, scoring rubrics, and interviewer calibration for a specified role.
incident-commander
Coordinate active incidents through severity assessment, roles, mitigation, communications, recovery verification, and postmortem handoff.
lark-task
A task-management skill for Lark, the collaboration platform, covering tasks, checklists, subtasks, assignments, attachments, and task-focused agents.
linear
A skill for managing Linear, a project-management tool for software teams, through its API. It works with issues, projects, teams, and collaboration data.