Hermes Guide

Good to know before installing

Reads config.yaml, SKILL.md frontmatter, skill bundles, plugin manifests, the shell-hooks allowlist and the built-in MEMORY.md/USER.md stores read-only (the report quotes short memory snippets); the sessions scope reads the tail of logs/agent.log read-only for runaway-session signatures (session ids, model names and token counts appear in the report); the update scope reads the update-lock record in the co-located hermes-agent checkout under $HERMES_HOME and probes it — owner-PID liveness, then a brief lock acquisition it releases immediately, opening the lock file writable, with a read-only fallback for a root-owned lock on POSIX (writes no content, never deletes the lock); registers one read-only plugin skill, hermes-guide:start, listed in model sessions while the plugin is enabled; /hermes-doctor and hermes guide run hermes config path as a subprocess (argument list, no shell); the default hooks check reads hook configuration, consent state and the exec bit in-process and executes nothing, while hooks --deep runs hermes hooks doctor, which executes every approved shell hook once with a synthetic payload (--fast starts no subprocess and executes no hook); /hermes-doctor and herme

From the plugin's catalog listing.