hermes-agent-plugins

A collection of hermes-agent plugins. Each top-level directory is one installable plugin.

Community plugins for hermes-agent — not officially affiliated with or endorsed by Nous Research.

🚧 Work in progress — actively developed; structure and plugins may still change.

These plugins install into the hermes plugin system directly — each lands in ~/.hermes/plugins/<name>/ and is gated by plugins.enabled. The hermes plugins install command does this for you straight from GitHub, including from a subdirectory of a monorepo like this one.

Plugins

Plugin	What it does	Status
google_meet	Create + join a Google Meet, transcribe live captions, optionally speak in-call, and follow up afterwards.	✅

(more to come — add a new top-level directory per plugin, each with its own plugin.yaml.)

Install

# Install one plugin from its subdirectory in this monorepo, and enable it.
hermes plugins install douinc/hermes-agent-plugins/google_meet --enable

# Or install disabled, then enable later.
hermes plugins install douinc/hermes-agent-plugins/google_meet --no-enable
hermes plugins enable google_meet

This clones the subdirectory into ~/.hermes/plugins/google_meet/ and gates it via plugins.enabled in your hermes config. Manage with:

hermes plugins list
hermes plugins update google_meet
hermes plugins remove google_meet

Manual install (no network / air-gapped)

cp -r google_meet ~/.hermes/plugins/google_meet
# then enable it
hermes plugins enable google_meet

Per-plugin setup

Each plugin documents its own prerequisites in its directory README. For google_meet you must run its one-time browser auth (hermes meet auth) so the bot joins with a signed-in Google session — see google_meet/README.md.

Plugins vs. skills (optional orchestration)

Installing a plugin gives you its tools (and CLI) — that is all you need to use it. Some plugins also ship an optional orchestration skill under examples/ that encodes higher-level conventions for the agent (e.g. google_meet's create → join → transcript → summary flow).

Skills are not installed by hermes plugins install, and are never auto-written into ~/.hermes/skills/. This is deliberate: a skill you have customized must never be silently overwritten. To use one, copy it in yourself and adapt it for your setup:

cp -r examples/google-meet-assistant-skill ~/.hermes/skills/google-meet-assistant
# then edit it for your chat platform / caption language / team calendar

The plugin's tools work fully without any skill.

Security

Runtime artifacts — signed-in browser sessions (auth.json), meeting transcripts, and tokens — are sensitive and live outside this repo under your hermes home; never commit them. The optional remote-node server binds to localhost and uses a bearer token but has no TLS, so don't expose it beyond a trusted network. See SECURITY.md for the full notes (and how to report a vulnerability).

Contributing

Contributions are welcome — this repo is actively developed. Open an issue or PR to add a plugin, fix a bug, or improve docs. New plugins go in their own top-level directory with a plugin.yaml (use google_meet/ as a template).

License

MIT — see LICENSE.