# 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 hundreds of 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: 273

## 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' public subagent lifecycle.

Each tool is registered with Hermes' complete function-tool schema, including
its name, description, and JSON `parameters`. The available arguments are:

| Tool | Arguments |
| --- | --- |
| `agency_agents_search` | `query` (required), optional `division` and `limit` |
| `agency_agents_inspect` | `agent` or `slug`, optional `include_body` |
| `agency_agents_load` | `agent` or `slug`, optional `task` |
| `agency_agents_delegate` | `agent` or `slug`, `task` (required) |

A normal flow is: search by capability, take a returned `slug`, then inspect,
load, or delegate to that specialist. You can ask Hermes to do this in natural
language; direct tool calls are not required.

## 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`.

Restart Hermes or start a new session after installing so the plugin and its
tool schemas are loaded. If Hermes displays these tools without their documented
arguments, regenerate and reinstall the plugin from the latest Agency Agents
checkout, then restart Hermes.
