Add Hermes lazy Agency router plugin (#614)

* Add Hermes lazy agency router plugin

* Document Hermes router specialist usage
This commit is contained in:
PattrnData
2026-06-28 14:27:39 +01:00
committed by GitHub
parent 1189f0f9bc
commit 8ab8d82930
6 changed files with 692 additions and 7 deletions
+60
View File
@@ -0,0 +1,60 @@
# Hermes Agency Agents Router Plugin
Generated by `scripts/convert.sh --tool hermes`.
This integration installs one Hermes plugin named `agency-agents-router` instead
of adding 232+ generated skills to `skills.external_dirs`. Hermes sees a
small fixed tool surface at startup, while the complete Agency roster is
stored on disk in `data/agents.json` and searched/loaded lazily.
Generated agent count: 232
## Tools exposed to Hermes
- `agency_agents_search` — find matching specialists by query/division.
- `agency_agents_inspect` — inspect one specialist's metadata or full body.
- `agency_agents_load` — compose one specialist prompt for the current task.
- `agency_agents_delegate` — delegate through Hermes `delegate_task` when available.
## Specialist usage instruction for Hermes
When a Hermes project needs Agency specialists, explicitly ask Hermes to use
the `agency-agents-router` plugin/router and load only the specialists needed for
the current phase. Do not ask Hermes to install or preload the full Agency
roster as skills.
Recommended project instruction:
```text
Use the agency-agents-router plugin. Search the Agency roster for the right
specialists, then load or delegate only the specific agents needed for each
part of the project. For multi-discipline projects, use multiple selected
specialists across the project, but keep routing lazy: do not preload the
full Agency roster and do not add agency-agents to skills.external_dirs.
```
Example:
```text
For this Data Swami build, use the agency-agents-router plugin to pick
relevant Agency specialists. Search first, then delegate to selected agents
such as frontend, backend, UX, QA, data engineering, and product strategy as
needed. Load/delegate each specialist on demand rather than loading all
Agency agents at startup.
```
## Install
```bash
./scripts/convert.sh --tool hermes
./scripts/install.sh --tool hermes
```
The installer copies the generated plugin to:
```text
${HERMES_HOME:-~/.hermes}/plugins/agency-agents-router
```
It then enables `agency-agents-router` under `plugins.enabled` in the Hermes
config. It does **not** write to `skills.external_dirs`.