// Use when creating, updating, validating, or explaining the agent registry for a Hermes Agent Control Room.
Use when creating a fresh Hetzner Cloud VPS with an SSH alias, local project folder, provisioning script, destroy script, and optional handoff into setup-control-room.
Use when bootstrapping an SSH-accessible Ubuntu/Debian VPS with the Agent Control Room template, core agent tooling, and linked control-room skills.
Use when designing, auditing, or documenting backups for Hermes agents without committing secrets.
Use when managing the Agent Control Room: documenting Hermes agents, adding agent folders, updating runbooks, checking architecture, mapping env vars without values, or keeping the control room source of truth consistent.
Use when auditing a VPS-based Hermes agent setup for exposed dashboards, weak secret handling, broad keys, Docker risks, or missing backup/security documentation.
Use when an orchestrator needs to route work to specialist Hermes agents through a task bus, create task briefs, check outboxes, or summarize delegated results.
| name | agent-registry-manager |
| description | Use when creating, updating, validating, or explaining the agent registry for a Hermes Agent Control Room. |
Maintain the registry that tells the orchestrator which agents exist and what they do.
Default registry path:
/srv/agent-bus/registry/agents.yaml
Each registry entry should include:
Do not store secrets in the registry.