Agent Templates
From its catalog listing
Share a whole Hermes agent as one .htemplate bundle and install it from a single HTTPS link: identity (SOUL.md), config with accounts and endpoints stripped, skills, routines, MCP server definitions, memories only when the author opts in, and plugin ids. A recipe, not a clone — credentials, sessions, conversation history, logs, caches and workspace never travel. Publish puts the bundle in a GitHub repository and returns one permanent link (re-publishing updates the same URL); Install previews a link, a path or a dropped file and shows the template itself before anything is written (SOUL.md, each skill, every routine's schedule and prompt, every MCP command, risky settings such as hooks with their values). Install enforces what the packer promises on any bundle: config sanitized again (approval and consent policy — command_allowlist, hooks_auto_accept, approvals, security — is always removed and the preview shows what was removed), routines imported paused through Hermes' cron API, MCP servers set enabled: false; plugins already installed here are enabled unless --no-enable-plugins. Reinstalling the same link offers "Update v1.0.0 → v1.1.0" and keeps memories, sessions and .env.
Good to know before installing
reads the selected profile under HERMES_HOME (config.yaml, SOUL.md, skills/, cron/jobs.json, mcp.json, memories/ when opted in) and writes a new profile directory plus its own bundles under plugin-data/; the page may read a bundle only from HERMES_HOME or the home directory, the CLI has no such limit. Network: one HTTPS GET to a URL the user pastes (HTTPS and public hosts only on the page; http, LAN and local accepted in the CLI; every redirect re-checked, 20 MB cap) and, only when the user presses Publish, the GitHub REST API to upload the bundle and download it back to prove the link before it is shown; republishing writes the file at the same public URL. Installs drop approval and consent policy (command_allowlist, hooks_auto_accept, approvals, security), import routines paused and turn MCP servers off; plugins already installed here are enabled unless --no-enable-plugins. Credentials: the optional GITHUB_TOKEN is read with agent.secret_scope under the named profile, never stored in a bundle, logged or returned. No shell, no telemetry, no self-updater.
From its catalog listing.
How to install
- Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install hermes-templates - Said no? Turn it on later:
hermes plugins enable hermes-templates - Restart Hermes so it loads the plugin.
Some plugins also need a sign-in or settings: see Full setup & settings. Memory plugins ask whether to become your memory provider instead. Steps follow the official plugins guide (opens in a new tab).
- Category
- Hermes Desktop add-ons · Security & privacy
- Maintained by
- Ilyassbm (Community)
- Needs
- No API keys declared
- Needs Hermes
- 0.23.0 or newer
- Version
- 1.3.1
- In the catalog
- 2026-11-15
Known issues (from its catalog listing)
- The Desktop half of a unified package starts disabled per browser; enable it once in Capabilities ▸ Plugins.
- raw.githubusercontent.com caches plain links for up to 5 minutes per client kind, so a just-published update can briefly still serve the previous file; the result also shows the commit-pinned URL, which is immediate.
- A profile named by ?profile= is only used for credential resolution; the page lists the profiles of the Hermes home it runs in.
Using the Hermes desktop app? See where plugins live

Full setup & settings ↗Source code ↗
More in hermes desktop add-ons
All hermes desktop add-ons plugins
New Hermes Agent updates every day on X. Follow @HermesWatcher