AgentPlaybooks Tools for Hermes

This Agent Plugins package installs the agentplaybooks-tools Hermes skill. It guides setup of AgentPlaybooks skills, MCP servers, and federated OpenAPI tools in the selected Hermes profile, including the authentication those connections need.

The package itself does not copy credentials, edit configuration in the background, or register tools. It guides you through the AgentPlaybooks CLI and Hermes profile setup. Review each plan before applying it.

Install

hermes plugins install matebenyovszky/agentplaybooks/packages/hermes-portable/agentplaybooks-tools --no-enable
hermes plugins enable agentplaybooks-tools
npm install -g @agentplaybooks/cli@0.5.0
apb --version

Hermes needs Node.js 20 or newer to run the CLI. Install the CLI separately; installing this skill does not install npm packages or require a hosted account. For a remote Hermes gateway, Node.js and apb must be available on the gateway host/container, and commands must target the profile that runs there. Installing the skill into a remote profile does not install the CLI on your Mac or gateway.

Connect playbook tools to Hermes

To let Hermes call a hosted playbook's MCP tools, including its federated MCP/OpenAPI services, preview a playbook-scoped connection:

apb login
apb connect <playbook-guid> --target=hermes

After reviewing the plan, apply it:

apb connect <playbook-guid> --target=hermes --apply

The plan reports which key environment variable the connection expects. Set a playbook-scoped API key in the selected Hermes profile's secret environment. For an account-wide connection, use apb connect --account --target=hermes instead and set AGENTPLAYBOOKS_API_KEY.

To install a private playbook's skills into the local project, separately preview and apply apb pull <playbook-guid> . followed by apb sync . --target=hermes. The pull restores the skills; sync registers them in Hermes's profile. Public skills can also be installed directly from a playbook's /.well-known/skills/ URL.

Authentication and secrets

apb login authenticates the CLI to AgentPlaybooks with a user API key. The key is stored in the CLI credential store, not in a skill or playbook file.
apb connect --account --target=hermes configures the account MCP connection. It refers to AGENTPLAYBOOKS_API_KEY; configure that secret in the environment used by the selected Hermes profile and restart Hermes if needed. An account key can reach account-wide tools, so prefer a scoped connection when it covers the required workflow.
apb connect <playbook-guid> --target=hermes configures a single playbook connection. Its plan shows the environment variable name (by default APBKS_KEY_AGENTPLAYBOOKS). Use a playbook-scoped key with only the permissions the connection needs, and set it in Hermes's profile secret store or environment, never in config.yaml, mcp.json, or the skill.
Federated MCP and OpenAPI credentials belong in the AgentPlaybooks vault. Hermes can call the playbook's tools without putting those upstream secret values in the Hermes configuration.

Use apb sync to register skills and merge MCP definitions already present in the local playbook project into Hermes. Review its plan before applying it.

Safety

apb sync, apb pull, and apb connect show a plan and make no local changes without --apply. apb pull --apply and apb sync --apply write to the selected Hermes profile. apb push --apply uploads the reviewed project configuration to AgentPlaybooks. Secret values are never included in that upload.

See the CLI guide and Hermes integration guide for details.

MIT licensed; see LICENSE.

agentplaybooks-tools

README