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 witt3rd/oh-my-hermes --skill omh-triagegit clone --depth 1 https://github.com/witt3rd/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/witt3rd/oh-my-hermes/omh-triage)<a href="https://agentmods.dev/skills/witt3rd/oh-my-hermes/omh-triage"><img src="https://agentmods.dev/badge/skills/witt3rd/oh-my-hermes/omh-triage/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/witt3rd/oh-my-hermes/omh-triage"><img src="https://agentmods.dev/badge/skills/witt3rd/oh-my-hermes/omh-triage.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.00015 | $0.02868 |
| Opus 5 | $0.00008 | $0.01434 |
| Sonnet 5 | $0.00003 | $0.00574 |
| Haiku 4.5 | $0.00002 | $0.00287 |
Grade A, and why
omh-triage 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 11d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OMH Triage — Consensus Backlog Grooming
v0.1 status: This skill is deliberately small. It ships with two roles (Maintainer, Skeptic) and is being battle-tested before more roles are added. The full design hypothesis (Maintainer / Operator / Architect / Member-advocate / Skeptic) lives in witt3rd/oh-my-hermes#9. The next concrete milestone (Operator role for version-cut planning pressure) is tracked at witt3rd/oh-my-hermes#11. Roles will be added as lived rounds surface real tensions that the current set cannot represent. The discipline here is learn through use, then expand — the inverse of authoring all five roles up-front against imagined friction.
When to Use
- Periodically grooming an issue backlog (default cadence: before each version cut, when ≥10 issues have accumulated since the last pass, or when a major refactor/migration just landed and may have moved issue premises)
- After a fast-moving development arc (multiple migrations or refactors in days/weeks) that may have superseded several open issues
- When the user says: "triage", "groom the backlog", "walk the issues", "what's stale"
When NOT to Use
- A single ambiguous issue that needs design (use
omh-deep-interviewthenomh-ralplan) - A backlog that's never been groomed and has hundreds of issues (do a manual first-pass cull first; this skill is for keeping a curated backlog honest, not for archaeology on a rotted one)
- Closing during active dev (don't mix the two-mode discipline — capture during dev, decide during grooming; see the host project's
docs/triage/PROCESS.mdif it has one)
Prerequisites
- A target repo with an issue backlog (GitHub Issues; pluggable for other backlogs eventually)
- Optional: a GitHub Project for version + cluster + status targeting (the run will write back to it)
- Optional: prior triage docs under
docs/triage/for delta-since-last-pass framing - The
delegate_tasktool must be available
What ships with it
2 files 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.
- 11d ago First seen · 184 lines · 15 tokens per session scan A c3c46ea7d1d5
omh-triage is a skill published in the GitHub repository witt3rd/oh-my-hermes (322 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 2,868 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.