Onboard a new model generation or sibling into oh-my-hermes: probe router recognition, research the official contract, write trait-to-counter calibration, place routing in both lanes, price from documented list only, gate machine config on a served route, prove with the gates, close with a benchmark pair. Use when a model family ships a new generation (for example "Fable 5.1 is out", "GLM 5.4 shipped", "onboard new model", "add model to chains").
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
The procedure lives in docs/MODEL-ONBOARDING.md.
Read that file and follow it in order.
It is kept there rather than here because Codex, Hermes handoffs, and generic
executor profiles run the same loop, and AGENTS.md requires that no single
executor own a shared surface. This file exists so the loop is reachable as
/model-onboarding; it holds no rules of its own.
Start by reading, in this order:
cat docs/MODEL-ONBOARDING.md
cat MODEL_OPTI.md
Nine things the loop gets wrong most often:
omh coding model-route first; a model_family of unknown
means the calibration never attaches. Probe the dated snapshot form too
(<id>-YYYY-MM-DD): some providers serve only that spelling, and it must
resolve the base's contract, chain position, price, and HUD label through
dated_snapshot_base() rather than falling to generic.deepseek-flash and 400s deepseek-v4.1-flash;
the versioned contract sits behind the pointer as a declared projection
and in EXACT_CONTRACT_POINTER_ALIASES..omc/research/; the Hermes lane is the one that
shows what the wire carries (id folding, effort overrides, passback).model-setup skill text, seven public doc surfaces,
the release budget note, and the pinned-chain tests all name the old id;
grep src/ tests/ docs/ README* site/ for it and move every site in the
same commit. Superseded generations leave the shipped chains (owner
decision, 2026-09-11) and join the recognition-only list; pins hide in
fixtures, so start the full suite in the background at the chain edit.model-providers.json. Place the id
with omh model-chains set, never by hand-editing the JSON; an operator
may keep an older generation behind it there, the shipped table does not.hermes --oneshot call
and read the usage file (model, provider, cost_status) before any
measurement or placement; gateways want the vendor-prefixed id.family arm next to baseline and optimized; expect pass rate to tie
and read the paired token delta, tool calls, and turns. Same pass with
more tokens on the tasks it fails is a sentence that pushes — cut it.-pro / -fast /
-flex aliases label their base id; self-review did not.Arguments pass through verbatim: the model ids as served (for example
claude-fable-5-1 claude-mythos-5-1).
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
[omh] Screen-reader or keyboard accessibility gaps: prepare WCAG, keyboard, focus, screen-reader, target-size, and reflow evidence gates for UI surfaces. Use when the user says: accessibility-audit, accessibility audit, a11y audit, a11y architect, wcag audit, wcag 2.2, wcag 2.2 aa, accessibility pass.
日本語の概要は準備中です。原文の説明を表示しています。
[omh] Hermes badges unlocked and achievement progress: achievements observation: summarize hermes-achievements badges, tiers, recent unlocks, and progress from local plugin artifacts. Use when the user says: achievements, achievement, badges, badge, my badges, show achievements, achievement summary, unlocked badges.
日本語の概要は準備中です。原文の説明を表示しています。
[omh] Technical proposal facing adversarial scrutiny: independent perspectives attack a proposal, then distill into a bundle a separate planner consumes. Use when the user says: adversarial-consensus, adversarial planning, adversarial plan review, red team this plan, red-team this plan, red team the proposal, multi-perspective review, multiple perspectives.
日本語の概要は準備中です。原文の説明を表示しています。
[omh] Coordinating several agents or profiles: coordinate multiple Hermes profiles or agents with task, handoff, heartbeat, blocker, and completion states. Use when the user says: agent-board, agent board, kanban, multi-agent, multi agent, multi agent board, multiple hermes agents, multiple hermes profiles.
日本語の概要は準備中です。原文の説明を表示しています。
[omh] Agent is stuck, looping, or drifting: capture a stuck, looping, drifting, or repeatedly failing agent run, diagnose the likely failure pattern, and prepare the smallest safe recovery action. Use when the user says: agent-debug, agent debug, agent debugging, agent introspection, agent self-debug, self-debug, self debugging, looping agent.
日本語の概要は準備中です。原文の説明を表示しています。
[omh] Choosing between coding agents on evidence: compare executor or agent choices on reproducible tasks using quality, cost, time, tool, and evidence metrics. Use when the user says: agent-evaluation, agent evaluation, agent eval, agent benchmark, executor evaluation, executor benchmark, compare agents, compare codex claude.
日本語の概要は準備中です。原文の説明を表示しています。