What is hermes-health-check?

A read-only diagnostic checklist for Hermes, a software gateway and automation service. It checks the installation, gateway, scheduled jobs, configuration, and recent errors, then explains fixes.

Use it when Hermes or its gateway or scheduled jobs are not working, after an update, or as a regular health check.

It turns scattered command output into a short list of specific problems and remedies without changing the system.

hermes-health-check — Skill for Claude Code and Codex by OnlyTerp

Install

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.

Any agent

npx skills add OnlyTerp/hermes-optimization-guide --skill hermes-health-check

Clone the repo

git clone --depth 1 https://github.com/OnlyTerp/hermes-optimization-guide

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/onlyterp/hermes-optimization-guide/hermes-health-check/github.svg)](https://agentmods.dev/skills/onlyterp/hermes-optimization-guide/hermes-health-check)

Your own site

<a href="https://agentmods.dev/skills/onlyterp/hermes-optimization-guide/hermes-health-check"><img src="https://agentmods.dev/badge/skills/onlyterp/hermes-optimization-guide/hermes-health-check/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/onlyterp/hermes-optimization-guide/hermes-health-check"><img src="https://agentmods.dev/badge/skills/onlyterp/hermes-optimization-guide/hermes-health-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 902 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00014	$0.00902
Opus 5.5	$0.00006	$0.00361
Sonnet 5.5	$0.00003	$0.00180
Haiku 4.5	$0.00001	$0.00090

Measured 21d ago against content hash 6da89aa7e8b2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

hermes-health-check 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 21d 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.

skills/hermes-health-check/SKILL.md · 85 lines

How it starts

The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Hermes Health Check

Run Hermes' own read-only diagnostics, then turn what they print into a short list of problems, each with the exact fix.

When to Use

The user says Hermes, the gateway, cron, or a platform "isn't working".
After hermes update, to confirm everything came back.
As a daily cron job on an always-on host.

Procedure

Run every command with the terminal tool. This skill only reads. See the pitfalls before suggesting any fix that writes.

Version and pending updates:
```
hermes --version
hermes update --check
```
Hermes' own diagnostics (read-only; never add --fix from inside a session):
```
hermes doctor
hermes status
hermes config check
```
Gateway and cron:
```
hermes gateway status
hermes cron status
hermes cron list
```
Cron fires only while a gateway runs. If hermes cron status warns that the gateway runs stale code, the fix is a gateway restart.

Recent errors:

hermes logs errors --since 24h
hermes logs gateway --since 24h --level WARNING

Map each finding to a fix. The most common ones:

Finding	Fix
No gateway running, so cron won't fire	`hermes gateway start`, or `hermes gateway install` if no service exists. Never add a system unit next to an existing user service: remove one first (`hermes gateway uninstall`).
Both a user and a system gateway service installed	Two services fight over the same bot tokens. Keep one and uninstall the other.
Gateway on stale code after an update	`hermes gateway restart`
Missing or outdated options	`hermes config check`, then `hermes config migrate`
"not a recognized config key"	Check the key name for a typo. v0.21.4 also prints this for some real keys (`agent.reasoning_effort`, `model_aliases.*`, `skills.creation_nudge_interval`), and for those it's harmless.
A platform's bot doesn't answer	Check that platform's allowlist or run `hermes pairing list`. Discord needs the Message Content intent.
"another Hermes process still holds an old copy of the session database's write-ahead log"	Stop every Hermes process, run `hermes doctor` until no holder is listed, then start one process
Version older than 0.21.2	Update. That release fixed a class of session-database corruption.

Read the full file on GitHub · 85 lines

Changes

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.

21d ago First seen · 85 lines · 14 tokens per session scan A 6da89aa7e8b2

Subscribe to this mod's changes

hermes-health-check is a skill published in the GitHub repository OnlyTerp/hermes-optimization-guide (696 stars, last pushed 22d ago), licensed MIT. It adds 14 tokens to every session and 902 once invoked, about $0.0001 per session on Opus 5.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-25.

Debugging DevOps and cloud

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

deck-retro

Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…

asheshgoplani/agent-deck · 86 tokens