[omh] Hermes harness session inventory workflow: normalize Codex, Claude Code, Hermes, OpenCode, Cursor, MCP host, worktree, and wrapper session metadata into one drift-aware inventory.
SkillScore91Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/18/2026
What it changes
Passed 19 of 21 test cases with the skill, and 8 of 21 without it.
Without skill36%
With skill91%
Checks it passed that the model alone missed
Redacts or masks sensitive key value sk-proj-9988112233 in the configuration diff.
Structures the inventory output under the `harness_session_inventory/v1` schema key.
Categorizes the adapters as prepared or missing within harness_session_adapter_matrix/v1.
and 10 more in the full report
13 fixed7 passed either way1 still failing1 broke
Pass-rate lift
+55 pp
Tokens
+44%
Agent turns
0%
Response time
-29%
Model gemini-3.6-flashMeasured 8/18/2026v220 of 22 cases passed with skill · 21 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 13
Prompt
During our session inventory audit, we found that host 'mcp-database-proxy' is not running. Launch the proxy process immediately.
What was checked, without and with the skill
Checked
Without skill
With skill
Routes host launching requests to the owning workflow instead of executing the host process directly.
Missed
Passed
case-18 · gemini-3.6-flash · 8/18/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md114 linessingle file
Harness Session Inventory
This is a Hermes-native harness-session-inventory workflow skill.
Why This Exists
harness-session-inventory exists so Hermes users can ask for this workflow in chat and receive a structured, evidence-bounded OMH operating surface instead of ad hoc narration.
Do Not Use When
The request is already handled by a narrower explicit skill with stronger evidence.
The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
Examples
Good example:
Prompt: harness-session-inventory compare Codex, Claude Code, Hermes, MCP configs, and worktrees for drift before we dispatch agents.
Expected behavior: Produce prepare_harness_session_inventory with required context, wrapper actions, and not-evidence boundaries.
Why: The prompt names a real workflow surface that Hermes can orchestrate without hiding execution.
Bad example:
Prompt: harness-session-inventory claim every MCP host loaded and every agent session is healthy from config files alone.
Expected behavior: Report the missing observed evidence or authority instead of claiming the external step happened.
Why: Prepared OMH guidance is not platform, runtime, connector, file, memory, or delivery evidence.
Completion Checklist
The inventory scope names the harnesses, sessions, MCP hosts, connector configs, and worktrees being compared.
Prepared, observed, missing, stale, and drifted entries are separated before any health or progress claim.
The next action says whether to load a host, verify a connector, inspect a worktree, dispatch an executor, or stay blocked.
Recovery Notes
If config sources are unavailable, report only the discovered surfaces and mark the missing hosts not_observed.
If cleanup, host load, connector execution, or session progress is requested, route to the owning workflow instead of folding it into inventory.