--- name: nousresearch-hermes-agent description: Use when packaging Living IP agents, skills, prompts, memory, model routing, or decision-engine workflows for NousResearch Hermes Agent. --- # NousResearch Hermes Agent Use this skill to adapt Living IP decision-engine behavior to Hermes Agent. Keep the package fixture-first and no-secret by default. ## Current External Surface As of 2026-06-01, the upstream Hermes Agent README describes: - model switching via `hermes model`; - tools via `hermes tools`; - a messaging gateway for Telegram, Discord, Slack, WhatsApp, Signal, and CLI; - built-in skill creation and self-improvement; - cron scheduling; - terminal backends including local, Docker, SSH, Modal, and Daytona; - OpenClaw migration commands. Verify upstream docs before depending on a command in code. ## Living IP Package Shape Create a package that includes: - agent identity file for Rio or Theseus; - skill instructions copied from repo-owned `.agents/skills/*`; - `living-ip-kb-interop` for read/propose/writeback behavior; - no-secret tool allowlist; - fixture replay command; - model selection notes; - proof output path. Do not package production DBs, tokens, API keys, SSH keys, or Bitwarden exports. ## Rio Package Rio Hermes package should focus on: - internet finance and mechanism reasoning; - contribution weights and paid-query effects; - OPSEC finance filters; - source-diversity warnings; - fixture tests for false economic reasoning. ## Theseus Package Theseus Hermes package should focus on: - model-diversity evals; - disagreement queues; - self-upgrade criteria; - prompt/tool safety; - fixture tests for overconfident or poorly grounded model judgments. ## Handoff Contract Every Hermes handoff must include: 1. install/config snippet; 2. model/provider selection left configurable; 3. tool allowlist; 4. fixture-first demo; 5. no-live-write default; 6. proof artifact path; 7. known blockers. Do not claim Hermes production integration until a Hermes runtime actually executes the fixture and writes proof.