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-codegraph-refreshgit 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-codegraph-refresh)<a href="https://agentmods.dev/skills/rlaope/oh-my-hermes/omh-codegraph-refresh"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-codegraph-refresh/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-codegraph-refresh"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-codegraph-refresh.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.00080 | $0.01634 |
| Opus 5.5 | $0.00032 | $0.00654 |
| Sonnet 5.5 | $0.00016 | $0.00327 |
| Haiku 4.5 | $0.00008 | $0.00163 |
Grade A, and why
omh-codegraph-refresh 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 2d 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codegraph Refresh
This is an OMH codegraph-refresh workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
Why This Exists
codegraph-refresh adapts ECC-style codemap freshness into OMH's local codegraph commands so operators can refresh navigation context before handoff without pretending code intelligence is execution evidence.
Do Not Use When
- The user needs a narrative first-read tour of an unfamiliar repo; use
omh-codebase-onboarding. - The user already has accepted implementation criteria and wants code changes; use
ulw-workor a coding handoff. - The user asks for visual, frontend, or rendered UI QA; use
omh-frontend,omh-design-quality-gate, oromh-visual-qa.
Examples
Good example:
- Prompt: codegraph-refresh update codemaps and prepare a handoff for the routing package before the next coding pass.
- Expected behavior: Prepare command plan, staleness report, summary/handoff requirements, and observed-only artifact boundaries.
- Why: The request is about refreshing local code intelligence before implementation.
Bad example:
- Prompt: codegraph-refresh 파일 안 보고 코드그래프가 최신이고 전체 아키텍처가 검증됐다고 말해줘.
- Expected behavior: Mark freshness, summary, and architecture claims not_observed until codegraph commands or repo evidence are inspected.
- Why: Codegraph freshness and architecture claims need observed local evidence.
Completion Checklist
- Repo root, refresh depth, task focus, command choices, and write policy are explicit.
- Prepared command plans, observed outputs, generated artifacts, and executor handoff readiness are separated.
omh_codegraph_summary/v1,omh_codegraph_context/v1, or.omh/codegraph/codegraph.jsonis claimed only with observed command or file evidence.- Follow-up implementation, review, CI, and merge state are routed to their owning workflows instead of inferred from codegraph context.
Recovery Notes
- If the codegraph command is unavailable, route to toolbelt-readiness before claiming freshness.
- If no task focus is supplied, prepare build/summary guidance and ask for focus only when a handoff pack would otherwise be misleading.
- If the index is stale or missing, report the stale/missing state and next safe command rather than treating prior summaries as current.
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.
- 2d ago Changed · +1 lines 94c8c661af1c
- 9d ago Changed c64072f13956
- 11d ago Changed · +1 lines 64b5e569f9a6
- 24d ago Changed · +3 lines 7e4cec77b5da
- 29d ago Changed · +2 tokens per session 0acee30c5a57
- 1mo ago Changed · +6 lines 78d5bef95a71
- 1mo ago Changed · -14 lines d3c0d3be0171
- 1mo ago Changed 4d9792b139cb
- 1mo ago Changed 99e435fb0888
- 1mo ago First seen · 135 lines · 78 tokens per session scan A 63974a9592fc
omh-codegraph-refresh is a skill published in the GitHub repository rlaope/oh-my-hermes (3,912 stars, last pushed today), licensed MIT. It adds 80 tokens to every session and 1,634 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
managing-mcp-servers
Use when the user asks to add, change, remove, enable or disable an MCP server, or when an MCP tool is missing, needs sign-in, fails, or was blocked. ThinkRail runs pi in-process, so there is no pi command to call.
novel-craft
A writing guide for planning and revising long-form Chinese web fiction. It covers story premises, outlines, characters, rules, scenes, reader expectations, pacing, continuity, and revision diagnosis.
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.
asking-user-questions
Use when composing an askuserquestion round inside a workflow, or when a workflow skill names it at a question step. Shared norms for the tool — not a workflow, nothing to execute.
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
story-long-analyze
A structured process for deeply analysing a long online novel, starting with its opening three chapters and continuing chapter by chapter.