Ops Observability Card

This is a Hermes-native ops-observability-card workflow skill.

Why This Exists

ops-observability-card exists so service, loop, and automation operations get one board where each cost, latency, token, failure-mode, and metric-provider figure is marked observed or prepared, instead of an improvised dashboard.

Do Not Use When

• The user asks what their own Hermes conversation has used or cost; Hermes' /usage shows this session's tokens and context, /insights estimates cost across recent sessions, and the omh_run_summary tool relays this conversation's recorded tokens and cost.
• The user wants one run's timing and context-budget report; use omh-run-efficiency.
• The user asks OMH to sign in to a metric provider, billing console, or dashboard and pull live figures; the card reads only supplied payloads and Hermes' own records.

Examples

Good example: