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-sales-developmentgit 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-sales-development)<a href="https://agentmods.dev/skills/rlaope/oh-my-hermes/omh-sales-development"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-sales-development/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-sales-development"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-sales-development.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.00057 | $0.01284 |
| Opus 5 | $0.00028 | $0.00642 |
| Sonnet 5 | $0.00011 | $0.00257 |
| Haiku 4.5 | $0.00006 | $0.00128 |
Grade A, and why
omh-sales-development 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sales Development
This is a Hermes-native sales-development workflow skill.
Why This Exists
sales-development prepares evidence-bounded discovery and qualification guidance without claiming sales execution.
Do Not Use When
- The user needs a company-level positioning, market-entry, or strategic-options decision rather than account-level discovery; use
strategy-brief. - The user supplies a CRM export or pipeline snapshot and needs portfolio health, aging, slipped deals, forecast calibration, or renewal-risk review; use
sales-pipeline-review. - The user only wants a polished social post, newsletter, or one-off outbound-copy rewrite; use
content-operator. - The user asks to send outreach, update Salesforce or HubSpot, create an opportunity, or book a meeting; use
connector-operatorwith explicit recipient, object, and authority. - The request asks for current competitor or company evidence but supplies no source material; begin with
researchbefore presenting claims as observed.
Examples
Good example:
- Prompt: Build a discovery plan and qualification questions for a mid-market prospect considering our support platform.
- Expected behavior: Prepare account evidence gaps, discovery and qualification questions, value hypotheses, and an owned next-step plan.
- Why: The request is account-level sales discovery, not outreach execution or company strategy.
Bad example:
- Prompt: Write a LinkedIn launch post for our new feature.
- Expected behavior: Route to
content-operator, notsales-development. - Why: A one-off social post has no account qualification or discovery objective.
Completion Checklist
- The decision, options, tradeoffs, assumptions, and rejected alternatives are named.
- Observed signals are separated from strategic inference.
- Accepted decisions and implementation follow-ups are not conflated.
Recovery Notes
- If evidence is mostly assumption, label it and recommend a research or feedback-triage pass.
- If the decision owner is missing, keep the output as options rather than accepted strategy.
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.
- 4d ago Changed · +1 lines 96dee9496f6b
- 7d ago Changed 49d8542c36e0
- 9d ago First seen · 128 lines · 57 tokens per session scan A dda402580639
omh-sales-development is a skill published in the GitHub repository rlaope/oh-my-hermes (1,677 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 1,284 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
story-long-analyze
A structured process for deeply analysing a long online novel, starting with its opening three chapters and continuing chapter by chapter.
story-review
A review process for finding problems in a novel’s structure, characters, wording, and world rules. It can use several reviewers or one reviewer when others are unavailable.
moxiangtongxiu-perspective
A Chinese-language creative-writing guide built around character-led stories, interwoven plotlines, memorable dialogue, ensemble casts, and emotional contrasts. It is presented as a perspective associated with the author Mo Xiang Tong Xiu.
tiancantudou-perspective
A creative-writing guide based on the storytelling patterns associated with Chinese web novelist Tiancan Tudou. It focuses on stories where an underestimated character grows stronger through challenges and moves into new settings.
tianya-gods-team
A decision-making system in which 20 fictional specialist viewpoints analyze one question in parallel before a coordinating AI combines them. It covers areas such as history, economics, relationships, technology, mysteries, and culture.
lijigang-skill
A Chinese-language approach to writing precise, highly structured prompts, sometimes using Lisp-like notation. It combines concise wording, philosophical questioning, and a process for defining roles, conditions, output formats, and revisions.