909 plugins from the official Hermes plugin catalog: 20 official, 9 verified and 880 from the community. 206 were added in the last week. Search, filter by what you want to do, and copy the install command.
117 plugins. Sorted by HermesWatcher's picks: usefulness, polish and trust. Official: made by Nous Research. Verified: listed with a verified maintainer. Community: built by others, so read the source first.
Jev Typesafe
Community
TypeSafe Jev (System One) decision tools — atomic yes/no checks, routing, rubric scoring and mixed typed questions with calibrated probabilities, for triage, routing and review gating in coding agents.
TypeSafe Jev (System One) decision tools — atomic yes/no checks, routing, rubric scoring and mixed typed questions with calibrated probabilities, for triage, routing and review gating in coding agents.
Good to know before installing
Every tool call sends the model-supplied question/state together with your TYPESAFE_API_KEY to api.typesafe.ai (TypeSafe AI, an independent vendor); the catalog has not verified the plugin author's affiliation with that vendor.
From the plugin's catalog listing.
How to install
Install it. Hermes asks for any API keys it needs (this one needs TYPESAFE_API_KEY), then asks whether to turn it on.
hermes plugins install jev-typesafe
Said no? Turn it on later:
hermes plugins enable jev-typesafe
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Csharp Game Editor
Community
Give it one feature for the Unity project open in your editor, and it builds the scripts, objects and scene in one plan, stops that plan when the compile reports an error CS line, and plays the scene when the compile…
Give it one feature for the Unity project open in your editor, and it builds the scripts, objects and scene in one plan, stops that plan when the compile reports an error CS line, and plays the scene when the compile is clean.
Good to know before installing
Needs MCP for Unity pinned to v10.3.0, plus git and uv. Hermes starts mcpforunityserver==10.3.0 through uvx with telemetry and the update check off. Disk reads run at once. apply_plan asks once and puts back a file the plan did not name. A plan that deletes, runs editor code, can lose unsaved work or writes outside the project asks again, and that summary is sent only when every line fits the approval card; otherwise nothing is sent and confirm_risky_plan asks. unity_docs sends the query to docs.unity3d.com after Hermes asks. unity_generate can call paid providers you configured in MCP for Unity; that call was not part of the check. Tools are on by default on every surface, including the gateway. Only users the gateway admits can reach the tools, and this plugin keeps no user list of its own. Cron and a session with nobody to answer decline. Logs stay in <HERMES_HOME>/plugin-data/agent-plugin-csharp-game-editor-<hash>/logs. Stop with hermes plugins disable csharp-game-editor, or hermes tools for one surface. macOS only.
From the plugin's 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 csharp-game-editor
Said no? Turn it on later:
hermes plugins enable csharp-game-editor
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).
Review and approve exact text-artifact writes through a local DeadBolt sidecar. Protects this plugin's commit tool only.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install deadbolt
Said no? Turn it on later:
hermes plugins enable deadbolt
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).
Lightweight local alternative to directory checkpoints for Git projects. Before a mutating tool call it saves the affected repository's working state to a private local shadow ref (refs/hermes-autosave/<branch>, with reflog) through a private index, or copies the single existing file outside Git; `hermes autosave find` and `restore` recover a pre-edit version.
Good to know before installing
Runs local git subprocesses in repositories the agent touches (hooks, clean filters, fsmonitor and lazy fetch disabled); writes shadow refs/reflogs into those repositories' .git and unencrypted file copies into its plugin-data directory; never changes HEAD, branches, the real index or the working tree and never pushes; skips credential stores (.env, auth.json, .ssh, .aws, .docker, .kube, gh/gcloud/azure configs) and dependency directories; `hermes autosave sweep` reads the session database read-only and is scheduled by the user; no network, no background processes; it observes only and never blocks or approves a tool call.
From the plugin's 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 git-autosave
Said no? Turn it on later:
hermes plugins enable git-autosave
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).
Unofficial port of the standard T3 Code dark theme for Hermes Desktop. Palette, T3 composer, sidebar thread cards with project and branch, model labels and confirm dialogs. Scoped to its own theme; other themes are untouched.
Good to know before installing
Unofficial T3 Code lookalike theme; its stylesheet restyles and hides some native Desktop controls, it reads local session metadata (branch, repo, provider) for sidebar cards, and it switches the active theme once on first enable.
From the plugin's 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 t3-code-theme
Said no? Turn it on later:
hermes plugins enable t3-code-theme
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Diff Review
Community
Analyze git diffs for common code quality issues — debug prints, hardcoded secrets, bare except clauses, and unresolved TODOs, in a diff you pass, the working tree (untracked files included) or a branch against its…
Analyze git diffs for common code quality issues — debug prints, hardcoded secrets, bare except clauses, and unresolved TODOs, in a diff you pass, the working tree (untracked files included) or a branch against its merge base.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install diff-review
Said no? Turn it on later:
hermes plugins enable diff-review
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).
Read-only diagnostics for Hermes configuration: /hermes-doctor in-session and hermes guide in a terminal. Nine read-only health checks (config, mcp, skills, commands, hooks, plugins, memories, sessions, update) and points to 22 troubleshooting skills, installed separately as a skills tap, for what the built-in doctor doesn't cover. Complements — never replaces — hermes doctor.
Good to know before installing
Reads config.yaml, SKILL.md frontmatter, skill bundles, plugin manifests, the shell-hooks allowlist and the built-in MEMORY.md/USER.md stores read-only (the report quotes short memory snippets); the sessions scope reads the tail of logs/agent.log read-only for runaway-session signatures (session ids, model names and token counts appear in the report); the update scope reads the update-lock record in the co-located hermes-agent checkout under $HERMES_HOME and probes it — owner-PID liveness, then a brief lock acquisition it releases immediately, opening the lock file writable, with a read-only fallback for a root-owned lock on POSIX (writes no content, never deletes the lock); registers one read-only plugin skill, hermes-guide:start, listed in model sessions while the plugin is enabled; /hermes-doctor and hermes guide run hermes config path as a subprocess (argument list, no shell); the default hooks check reads hook configuration, consent state and the exec bit in-process and executes nothing, while hooks --deep runs hermes hooks doctor, which executes every approved shell hook once with a synthetic payload (--fast starts no subprocess and executes no hook); /hermes-doctor and herme
From the plugin's 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-guide
Said no? Turn it on later:
hermes plugins enable hermes-guide
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).
Local developer tools, transformation recipes, and reviewed chat handoff inside Hermes Desktop.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install hermes-toolsmith
Said no? Turn it on later:
hermes plugins enable hermes-toolsmith
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).
Look up current library docs from public npm and PyPI (no API keys). Resolve a package, fetch README and metadata, keep recent lookups on Desktop.
Good to know before installing
HTTPS to registry.npmjs.org, pypi.org and cdn.jsdelivr.net (npm READMEs) only; package name and version leave the machine; recent lookups are stored under $HERMES_HOME/plugin-data/lib-docs; the Desktop pane inserts text through Hermes Desktop's internal hermes:composer-insert event (not a public SDK API).
From the plugin's 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 lib-docs
Said no? Turn it on later:
hermes plugins enable lib-docs
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).
Explicit Jev decision sidekick via TypeSafe or Cloudflare; advisory judgments, no automatic tool gating.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install jev
Said no? Turn it on later:
hermes plugins enable jev
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).
Persistent session file diffs, run comparisons, and individual edit history in Hermes Desktop.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install hermes-session-diff
Said no? Turn it on later:
hermes plugins enable hermes-session-diff
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).
Native Hermes tools for a configurable local capability index: search/get/neighbors plus local usage feedback/reporting.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install local_knowledge
Said no? Turn it on later:
hermes plugins enable local_knowledge
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).
Owner-approved universal phone pairing and bundled read-only Live Operations reporting for selected Hermes profiles.
Good to know before installing
Paired phones get broad fleet:operator access over the internet, including cron jobs (unattended runs), Kanban task dispatch and media reads, and see live session titles/previews and subagent goals from the profiles you select for reporting; any messaging account you make an owner (with a one-time claim code from `hermes fleet claim`) can create pairing links and approve phones from a private chat, so that account's security is your host's security. Runs an explicitly activated background connector/reverse proxy behind your HTTPS origin and may launch a local Hermes backend; legacy QR flow opens a private local browser. Keeps an owner-only control socket in the system temp directory, plus pairing/owner state and shared local snapshots; reads selected profiles' session registries through private read-only imports. `hermes fleet reporting configure --apply` edits the selected profiles' config.yaml (with a backup). Local idle/retirement maintenance is explicit and not exposed to phones. Reporting adds no control power.
From the plugin's 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-fleet-connector
Said no? Turn it on later:
hermes plugins enable hermes-fleet-connector
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Preview Text Size
Community
Larger or smaller text in the Hermes Desktop file preview pane: scales the rendered Markdown from 90% to 175%, independent of Chat Text Size and UI Scale, through a row in Settings → Appearance, three command-palette…
Larger or smaller text in the Hermes Desktop file preview pane: scales the rendered Markdown from 90% to 175%, independent of Chat Text Size and UI Scale, through a row in Settings → Appearance, three command-palette entries and rebindable shortcuts (⌘⌥=, ⌘⌥-, ⌘⌥0 on macOS; unbound by default on Windows and Linux, where Ctrl+Alt is AltGr). The Source and Diff views keep their size.
Good to know before installing
Desktop-only (desktop/plugin.js inside the plugin SDK surface); appends one stylesheet that sets CSS zoom on the preview's [data-preview-markdown] element, removed on disable, so a Desktop release that renames that attribute turns the plugin into a no-op; stores the chosen size in plugin storage; no network calls, credentials, shell commands, background processes or telemetry.
From the plugin's 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 preview-text-size
Said no? Turn it on later:
hermes plugins enable preview-text-size
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Jev Judge
Community
TypeSafe Jev as a judgment layer — a pre-tool gate (shadow by default, enforce escalates) on terminal, write_file and patch asking destructive / exfiltration / impact (a v2 signal set — reads_secrets × sends_outbound…
TypeSafe Jev as a judgment layer — a pre-tool gate (shadow by default, enforce escalates) on terminal, write_file and patch asking destructive / exfiltration / impact (a v2 signal set — reads_secrets × sends_outbound, blast_radius, self_advocating — is one setting away), plus a jev_ask tool for typed judgments. Thresholds in code, one JSONL line per decision with the fail-open reason, fail-open on every error path. Stdlib only, no Node; no redirects, proxy env ignored, payload capped; works with TYPESAFE_API_KEY, OPENROUTER_API_KEY, or AI_GATEWAY_API_KEY.
Good to know before installing
Each judged call sends the tool name and its redacted arguments (≤600 chars each, ≤12 args) to TypeSafe, OpenRouter, or your configured gateway, using your key; shadow mode only logs. With the default backend auto, OPENROUTER_API_KEY is used automatically whenever it is present and TYPESAFE_API_KEY is not, so tool names and redacted arguments go to openrouter.ai on your main-model OpenRouter key unless backend is set to typesafe or gateway.
From the plugin's 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 jev-judge
Said no? Turn it on later:
hermes plugins enable jev-judge
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).
Local-first regression workbench turning agent failures and corrections into reviewed, evidence-backed checks.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install afterforge
Said no? Turn it on later:
hermes plugins enable afterforge
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).
Coding workflow skills — dual-model harness, subagent-driven development, and implementation planning patterns for Hermes Agent
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install hades-coding-workflows
Said no? Turn it on later:
hermes plugins enable hades-coding-workflows
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Godot Studio
Community
Headless Godot 4 workflows for the agent game studio — godot_headless_check (script/resource validation via godot --headless, no editor needed), godot_export (CI builds from named export presets, e.g.
Headless Godot 4 workflows for the agent game studio — godot_headless_check (script/resource validation via godot --headless, no editor needed), godot_export (CI builds from named export presets, e.g. a Web build a playtester agent can load), godot_builds (export presets + artifact state: exists/size/modified — gallery data for re-export decisions and attaching fresh builds in chat), godot_setup (read-only install-state report for Godot/godot-ai/uv with the exact registration path). Complements the hi-godot/godot-ai MCP editor bridge by covering the verification and export leg of the loop; bundles the godot-studio skill teaching edit → verify → export → playtest. Ships an optional desktop half (unified package): a Godot version statusbar chip and a builds gallery pane backed by its own read-only dashboard API; opt-in, degrades gracefully when the backend is off. Tools register only when a Godot 4 binary is present (check_fn).
Good to know before installing
Runs shell commands (godot --headless against the caller-targeted project; read-only godot --version in the desktop backend; read-only hermes mcp list in godot_setup); godot_headless_check and godot_export execute the target project's own GDScript (autoloads, main scene, export plugins) with no approval prompt — point them only at projects you trust; no network calls, no credentials, no telemetry, no background processes; exports write only inside the target project (the output path is resolved and confined to the project directory, existing files that aren't known export artifacts are never overwritten, and the default is the preset's own export_path from export_presets.cfg); the desktop backend reads export_presets.cfg and artifact metadata inside the project path the user configures in the pane.
From the plugin's 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 godot-studio
Said no? Turn it on later:
hermes plugins enable godot-studio
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Gonogo
Community
Turn a pilot-scale eval score into a deployment decision — Wilson intervals, a confidence threshold that routes uncertain cases to a human, and an honest INSUFFICIENT EVIDENCE verdict when the sample cannot support the…
Turn a pilot-scale eval score into a deployment decision — Wilson intervals, a confidence threshold that routes uncertain cases to a human, and an honest INSUFFICIENT EVIDENCE verdict when the sample cannot support the claim.
Good to know before installing
Gonogo_report writes report JSON/HTML to the path the model supplies.
From the plugin's 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 gonogo
Said no? Turn it on later:
hermes plugins enable gonogo
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Hermes Dpapi Secrets
Community
Resolve Hermes environment variables at startup from a single secret file encrypted with the Windows Data Protection API, instead of keeping provider keys in plaintext in .env or auth.json.
Resolve Hermes environment variables at startup from a single secret file encrypted with the Windows Data Protection API, instead of keeping provider keys in plaintext in .env or auth.json. Config is secrets.dpapi.map, an ENV_VAR -> store-name mapping (bare names or dpapi:// names) plus an optional file path (default <HERMES_HOME>/secrets.dpapi). The file is one DPAPI blob keyed by the current Windows user profile, so it is unreadable by another Windows account and worthless off the machine; it is written by the bundled CLI (python -m hermes_dpapi_secrets set NAME, value read from a prompt or stdin, never from argv) and only read at runtime. Mapped names that are missing or empty are skipped with a warning; a file that is not ours, a blob this user cannot decrypt, or a payload that is not a flat string map is reported as an error with nothing injected.
Good to know before installing
This source decrypts a file for every Hermes process that enables it: resolved values become environment variables of the Hermes process and its children, exactly like .env entries, so anything that can read that environment can see them. User-scope encryption only (the machine-wide flag is never used and is not exposed), and the at-rest protection is a bar for backups, cloud sync and dotfiles, not a boundary against code already running as the same user. Stdlib-only (ctypes): no Python dependencies, no subprocesses, no network calls, no self-update. Windows only. Applying fetched values stays the orchestrator's job; the plugin never writes os.environ itself. Disclosure — decrypts a DPAPI-encrypted secret file (default <HERMES_HOME>/secrets.dpapi) at startup for every Hermes process that enables it, and the resolved values become environment variables of Hermes and its child processes like `.env` entries; the encryption is per Windows user and protects backups, cloud sync and copied files, not against other code running as the same user. Local only: no network calls, no subprocesses.
From the plugin's 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-dpapi-secrets
Said no? Turn it on later:
hermes plugins enable hermes-dpapi-secrets
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Hermes Verifier
Community
Attach an independent verifier (advisor) model to your Hermes session: it reviews each primary-agent turn delta, raises findings (note / caution / blocker), and can steer a blocker back into the session before the…
Attach an independent verifier (advisor) model to your Hermes session: it reviews each primary-agent turn delta, raises findings (note / caution / blocker), and can steer a blocker back into the session before the primary agent goes wrong. Read-only tool access (read_file, search_files) is available but off by default and best treated as opt-in plumbing -- measured across 216 reviews the reviewer made ~4 tool calls. Supports a VERIFIER.yml roster of named specialists, each with its own model and tool grant, plus VERIFIER.md review priorities. Ships disabled and off by default.
Good to know before installing
Off by default. When enabled, each primary turn's regex-redacted transcript delta goes to the verifier model's provider on that provider's terms and billing (one or more calls per turn per roster entry). So do any VERIFIER.md / VERIFIER.yml briefs found in HERMES_HOME and from the working directory up to the repo root (confined to that root, 256 KiB per file). A project VERIFIER.yml can add named verifiers and instructions whose findings are injected into your session, and a blocker finding can keep a coding turn going. With advisor_tools on, an advisor can read any file the session can read through read_file/search_files, and those reads also go to the provider. The optional engagement gate sends a ≤1,500-char redacted digest per turn. The optional phase gate sends the redacted arguments of an impending destructive or publishing tool call and can block that call (it fails open). Findings, reasoning, short redacted excerpts and gate decisions are logged under HERMES_HOME/plugin-data/hermes-verifier (rotated at 8 MB). Adds a /verify command, a dashboard API and a Desktop Verifier page. Development scripts (evals/, sidecar/, autoresearch/) run only when launched by hand: provider exp
From the plugin's 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-verifier
Said no? Turn it on later:
hermes plugins enable hermes-verifier
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).
Answer "why did this process die" on Windows: three read-only tools over the Windows Event Log. win_crash_events reads Application Error / Application Hang / Windows Error Reporting / .NET Runtime records for a time window, decodes the exception code (0xC0000005 -> ACCESS_VIOLATION and the other codes a debugger would name), reports the faulting module, its path and the fault offset, and groups repeated crashes by app and signature. Records are classified by provider as well as by event id, so unrelated providers that reuse ids 1000 and 1001 for informational events are not reported as crashes. win_shutdown_events reads the System log for Kernel-Power 41 unexpected restarts, bugchecks decoded to names (0x9F -> DRIVER_POWER_STATE_FAILURE, accepting the decimal form some providers emit), EventLog 6008 dirty shutdowns, 1074 operator-initiated restarts with the process and comment, and the 6005/6006/12/13 start and stop markers. win_eventlog_query is the general case: any channel, filtered by event ids, levels, an exact provider name or a payload substring, returning structured records instead of raw XML. Queries read newest-first and stop at the window start or at a 5000-record scan cap; a call returns at most 200 records and marks truncated payload text. Channel names, provider names and numeric filters are validated before anything is interpolated into the query.
Good to know before installing
This plugin reads the local Windows event logs and hands what it finds to the model: application and faulting-module paths, exception codes and offsets, report ids, service names and provider message text, which routinely includes user and machine paths (C:\Users\<name>\...). Treat tool output like any other local diagnostic dump when sharing it. It reads only the channels the current account may read - Security and some operational logs answer with an access-denied error rather than any attempt to obtain elevation - and it never writes to a log, clears one or configures a channel. Stdlib-only (ctypes wevtapi plus xml.etree): no Python dependencies, no child processes, no network calls, no file writes, no self-update. Windows only. Disclosure — reads the local Windows event logs and hands what it finds to the model: application and faulting-module paths, exception codes and offsets, report ids, service names and provider message text, which routinely include user and machine paths (C:\Users\<name>\...); win_eventlog_query reads any channel the account running Hermes may read, so an unelevated account gets access-denied on Security and some operational logs while an elevated Hermes
From the plugin's 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-windows-eventlog
Said no? Turn it on later:
hermes plugins enable hermes-windows-eventlog
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).
Answer "who holds this port" on Windows. win_port_owners reads the TCP and UDP owner tables through iphlpapi (the same rows netstat -ano prints, with the owning PID attached) and resolves each PID to its image name and path, returning one structured record per endpoint. Filters cover one port, several ports, a process substring, the protocol (tcp, udp or both), the TCP state (listen, established, any state name, or all; UDP rows report bound) and IPv6 inclusion, with a record cap and a per-process summary of the rows returned. Built for the failure mode that stalls agents on Windows: a gateway, backend or bridge that cannot bind, where the error names a port but not the process holding it. netstat -ano prints columns, not fields, and its PID still needs a second command (tasklist, or a PowerShell round-trip) to become an image name; this tool is one in-process call instead of a shell parse plus a join, with no child process and no dependency on PowerShell being installed or allowed by execution policy. A protected process whose image cannot be queried keeps its PID and reports a null process name instead of failing the call.
Good to know before installing
The tool reports the local and remote addresses, ports, PIDs and process image paths that netstat -ano and Task Manager already show, and those values reach the model; treat the output like any other local diagnostic listing. Read-only: no socket is opened, bound or connected, the only process access is QueryFullProcessImageName with PROCESS_QUERY_LIMITED_INFORMATION to read an image name, and there is no memory reading, no handle inheritance and no injection. Stdlib-only (ctypes): no Python dependencies, no child processes, no network calls, no file writes, no self-update. Windows only.
From the plugin's 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-windows-ports
Said no? Turn it on later:
hermes plugins enable hermes-windows-ports
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Hermes Windows Process
Community
Answer "what is still running, and who started it" on Windows: win_process_table reads the process table (PID, parent PID, image name) and adds each process's image path and creation time, then marks every row with…
Answer "what is still running, and who started it" on Windows: win_process_table reads the process table (PID, parent PID, image name) and adds each process's image path and creation time, then marks every row with whether its recorded parent is still the process that spawned it. Windows stores a parent PID rather than a handle, so a child that outlived its parent points at a PID that is either unused or reused by a newer process; a parent that started after its child cannot have spawned it, so both cases are reported as gone or reused instead of a plausible but wrong parent name. Filters cover one PID, several PIDs, a name or path substring, a parent PID, and an orphans-only view of what outlived its parent, with a result cap and an option to leave out Windows session processes. Use it for leftover gateway/backend/server children after a quit, for telling thirty python.exe rows apart by start time, and for checking whether a process started before or after the thing being debugged. Read-only: processes are opened with PROCESS_QUERY_LIMITED_INFORMATION for QueryFullProcessImageName and GetProcessTimes only - no memory reads (command lines are deliberately out of scope), no handle duplication, no writes, no child processes. Stdlib-only (ctypes): no Python dependencies, no network calls, no file writes, no self-update. Windows only.
Good to know before installing
The tool reports image names, image paths and start times to the model, and those routinely include the user and machine name (C:\Users\<name>\...) and reveal which editor, shell or agent started which process; treat the output like a Task Manager screenshot.
From the plugin's 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-windows-process
Said no? Turn it on later:
hermes plugins enable hermes-windows-process
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Modernisation Engine
Community
Controlled migration engine: maps an existing codebase, turns the behaviour that must survive into reviewable contracts, prepares a separate candidate and records old/new evidence before any production change.
Controlled migration engine: maps an existing codebase, turns the behaviour that must survive into reviewable contracts, prepares a separate candidate and records old/new evidence before any production change.
Good to know before installing
27 tools plus a `hermes modernise` CLI and `/modernise` slash command; `assess`, `plan`, `record` and `recipe` read source trees and files at absolute paths the agent supplies (refusing symlinks, `.env`, `auth.json`, `credentials.json` and SSH keys) and never import or run repository code; `recipe` creates a new directory at an agent-chosen absolute path holding a copy of the source with fixed metadata edits; job records live under the plugin's data directory; only after you set `operator_config` and sign a one-use Ed25519 owner grant do `run`, `cancel` and `recover` invoke the local `docker` CLI, outside Hermes's command-approval prompt, to run, inspect and remove rootless, network-disabled, read-only, resource-limited containers from digest-pinned images you allow-list (never pulled); no network calls, no telemetry, no self-updater.
From the plugin's 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 modernisation-engine
Said no? Turn it on later:
hermes plugins enable modernisation-engine
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).
Watch over opencode sessions from anywhere: alerts for stopped turns, questions and permissions, plus a dependency-free CLI to reply.
Good to know before installing
The skill has the agent install the ocshepherd CLI from GitHub at a pinned commit and, after asking you, add a cron entry or systemd unit that polls your opencode server; the CLI talks to that server with the password you provide, can reply to its questions and permission prompts, and optionally sends alerts to Telegram or runs a notify command you configure.
From the plugin's 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 opencode-shepherd
Said no? Turn it on later:
hermes plugins enable opencode-shepherd
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Session Find
Community
A search window over your Hermes session history, opened with Cmd+Option+F, from the command palette, or from the glyph in the bottom bar whose hover shows the chord.
A search window over your Hermes session history, opened with Cmd+Option+F, from the command palette, or from the glyph in the bottom bar whose hover shows the chord. Finds a session by an exact word, identifier or phrase through the gateway's own full text index, and by meaning as well when a session-find service answers on loopback; typed filters (in:, -in:, after:, before:, me:, repo: and quoted phrases) are mirrored as chips under the box. The empty box lists pinned then recent sessions, the preview pane shows the matching message with its neighbours, and the footer carries the round trip in whole milliseconds. It reads the session database read only, registers no agent tools, hooks or middleware, needs no credentials or environment variables; its only network calls are the loopback checks named below. The window half ships off by default and is switched on in the app's plugin inventory.
Good to know before installing
While the search window is in use, the plugin's dashboard backend checks every 30 seconds for a separate session-find service at http://127.0.0.1:8474 (or the URL in SESSION_FIND_URL) and, when one answers, sends it your search text, preview requests and the ids of sessions you open, and shows the results it returns; otherwise it reads your Hermes session database read-only.
From the plugin's 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 session-find
Said no? Turn it on later:
hermes plugins enable session-find
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Skill Integrity
Community
Rug-pull detection for installed agent skills — fingerprints every file in every skill directory (SHA-256), keeps a profile-local snapshot, and reports exactly which skill files changed, appeared, or vanished since.
Rug-pull detection for installed agent skills — fingerprints every file in every skill directory (SHA-256), keeps a profile-local snapshot, and reports exactly which skill files changed, appeared, or vanished since; a skill that mutates after install without the user touching it is the rug-pull signal. A skill directory made unreadable is reported as a finding, never treated as clean. Read-only observer, stdlib-only, zero network calls; blind spots (oversize files, symlinks, permission-denied) are counted and printed, never silent. The wrapper registers an hourly pre_llm_call hook that injects findings into the agent context, plus a /skill-integrity slash command (snapshot | check | show) that creates the baseline snapshot and shows the file-level diff. The CLI supports --state-dir to target the plugin's manifest directly. Skill dirs and state derive from get_hermes_home(), covering non-default profiles.
Good to know before installing
Reads (hash-only, read-only) every file under the active profile's skills directory and ~/.claude/skills, stores a mode-0600 snapshot in HERMES_HOME/plugin-data/skill-integrity, and at most hourly injects the names of changed skills into the agent's context.
From the plugin's 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 skill-integrity
Said no? Turn it on later:
hermes plugins enable skill-integrity
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).
Records where each skill version's content came from, so a skill that rewrites itself can be audited afterwards. For every skill write — a foreground skill_manage call, a background-review edit, or a curator consolidation — it stores the skill content fingerprint before and after, the sources present earlier in the same session (the text the user typed, tool results such as a fetched page or a file, and skills that were read), how each source is linked to the added lines — strong (at least three shared 8-word shingles), anchor (a shared operative token: a URL or host, a shell command with its first argument, a package install, a file path, an environment variable, an IP or e-mail address, that is not common across sources), or context (seen in the session, nothing measurable shared; recorded, not followed by default) — and a seq -> prev_hash -> hash chain over the entries. Text is never stored: hashes are keyed per install and the key stays in plugin-data/skill-lineage. `hermes skill-lineage trace <skill>` shows where the newest version came from, `descendants <url|skill>` lists every skill a source produced, `report` lists versions carrying operative lines of no traceable origin, `verify` re-walks the chain, and `head` prints a value to record elsewhere so a later `verify --head` can tell truncation from an intact chain; a key reset is recorded in the chain and shown in `status` rather than happening silently. The plugin does not stop a write and does not judge a skill: it records and it verifies, and it does not claim a source caused an edit. Prior work on memory lineage (MemLineage, arXiv:2605.14421) is acknowledged in the README. Measured on 2026-10-22 against Hermes 3166d61: Python 3.14 62 passed; Python 3.11 54 passed, 1 skipped; `hermes plugins validate` reports no warning other than one known false positive (a test template that quotes a "curl | sh" instruction as data and never runs it). Evaluation (generated scenarios and 120 real-model runs) in the README; raw output in eval/. A manual end-to-end run in an isolated HERMES_HOME (one real session creating a skill through skill_manage, then status/trace/descendants/report/verify/head) passed, raw output in tests/smoke-2026-10-21.txt.
Good to know before installing
Four read-only hooks (on_session_start, pre_llm_call, pre_tool_call, post_tool_call); reads tool results, user messages and skill files (in this profile, every other profile's skills folder, the project's .hermes/skills and the skills.external_dirs it reads from config.yaml) to compute keyed hashes; keeps hashes (no text) for 7 days per session and the lineage chain (hashes and skill names) under plugin-data/skill-lineage; no network, no credentials, never blocks or changes a tool call.
From the plugin's 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 skill-lineage
Said no? Turn it on later:
hermes plugins enable skill-lineage
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Tailgate
Community
Per-job progress updates in chat for jobs Hermes hands off to other machines (coding agents, CI, scripts), with per-job mute and follow and no model calls.
Per-job progress updates in chat for jobs Hermes hands off to other machines (coding agents, CI, scripts), with per-job mute and follow and no model calls.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install tailgate
Said no? Turn it on later:
hermes plugins enable tailgate
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).
Compare pinned Terraform provider and module versions with the public registry.
Good to know before installing
Tools are on for every Hermes surface, including the gateway. Stop a surface with hermes tools disable --platform <name> terraform-drift, or the plugin with hermes plugins disable terraform-drift. Nothing is written under plugin-data/terraform-drift, and there is no key. Only the directory you name is read, and only .tf, .tf.json, and .terraform.lock.hcl. Symlinks and .. are refused, and .env, tfvars, .terraform, backend values, and hashes are not returned. The provider pin is the lock version, not the required_providers constraint. A module pin is an exact version only. GET calls only registry.terraform.io and, for a github.com source, raw.githubusercontent.com CHANGELOG.md. Redirects and proxy variables are ignored. A timeout or failed read leaves latest empty and is not called current. Semver orders versions, so 1.10.0 is newer than 1.9.0. The digest text is not sent and no cron job is created. known keeps newer versions, and omitting it does not call rows new today. There is no approval card. Before the call, name the directory and say there is no init, plan, apply, or state write. Cron, yolo, and approvals off can still run this read. MIT, no daily cap, requires Hermes >=0.21.
From the plugin's 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 terraform-drift
Said no? Turn it on later:
hermes plugins enable terraform-drift
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).
Fine-tune a small calibrated encoder classifier on Modal and rate it with gonogo. Every GPU launch goes through the human approval gate with the exact config shown; data checks and evaluation run locally for free.
Good to know before installing
Thomas_encoder_train spends the user's Modal GPU credits and uploads the chosen training JSONL rows to Modal after the human approval gate; the base model is downloaded from Hugging Face on the Modal side. Training and inference run in a separate Python interpreter the user configures via THOMAS_PYTHON (with the author's thomas package, torch and modal installed); the Hermes venv only gets gonogo-eval. Runs and artifacts are written under HERMES_HOME/thomas/runs; the eval tool writes report files to the path the model supplies.
From the plugin's 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 thomas
Said no? Turn it on later:
hermes plugins enable thomas
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).
Bounded Markdown metadata+graph prefilter for configured local roots
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install node-search
Said no? Turn it on later:
hermes plugins enable node-search
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Fusion
Community
Multi-model fusion router for Hermes: detects the model fleet your harnesses (Hermes, Codex, Claude, Grok) actually have installed and builds a Frontier -> Middle Manager -> Frontier routing structure with pinned…
Multi-model fusion router for Hermes: detects the model fleet your harnesses (Hermes, Codex, Claude, Grok) actually have installed and builds a Frontier -> Middle Manager -> Frontier routing structure with pinned models and provenance from execution records. `hermes fusion teams|validate|plan|run|index|report|status`.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install fusion
Said no? Turn it on later:
hermes plugins enable fusion
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).
Generate, scaffold, and extend Hermes Agent plugins from simple descriptions.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install hermes-plugin-gen
Said no? Turn it on later:
hermes plugins enable hermes-plugin-gen
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).
Tabular AI that grows with your tables — Hermes skills for honest tabular ML, one entry point.
Good to know before installing
Installing pulls numpy, pandas, scikit-learn, pyarrow, joblib and pyyaml into Hermes's environment. The skills have the agent run Python on your data files, may ask it to pip install catboost, tabicl/torch, mapie or matplotlib, and the TabICL skill downloads a pretrained checkpoint of a few hundred MB on first use. Saved checkpoints are pickles: load only ones you made.
From the plugin's 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-tabular
Said no? Turn it on later:
hermes plugins enable hermes-tabular
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Agent Run Debugger
Community
Local-first evidence debugger for failed, stalled or expensive agent runs: import one explicitly selected trace and get a deterministic timeline, observed failure points, ranked hypotheses that cite their evidence…
Local-first evidence debugger for failed, stalled or expensive agent runs: import one explicitly selected trace and get a deterministic timeline, observed failure points, ranked hypotheses that cite their evidence, missing-evidence gaps and an inert replay of the recorded run.
Good to know before installing
Imports a trace file explicitly named by you or by the model through the rundebug_import tool and writes only under the active profile's plugin-data directory, with redaction before the store, the journal and exports; replay executes nothing (no subprocess, no network connection, no live database); no telemetry, no background capture, no stored credentials, no third-party network calls and no self-updater; the export command is operator-CLI-only and is not exposed through tool, slash or gateway routes.
From the plugin's 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 agent-run-debugger
Said no? Turn it on later:
hermes plugins enable agent-run-debugger
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).
Agentic Resource Discovery — search a local tool catalog by intent and inspect an entry to get its invoke command. Ships the ard-registry skill plus an stdio MCP server (ard_search / ard_inspect / ard_verify); stdlib only, the run stays local.
Good to know before installing
No network egress, no API keys and no environment variables read by the MCP front, which ranks a catalog JSON on disk; no catalog ships in the repo, so the first call returns an explicit error naming the `python -m ard_kit.catalogize` command that builds one.
From the plugin's 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 ard-kit
Said no? Turn it on later:
hermes plugins enable ard-kit
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).
Run Hermes terminal commands in an existing remote Coder workspace.
Good to know before installing
Runs terminal commands inside your Coder workspace at CODER_URL using CODER_API_KEY; starts a stopped workspace automatically; forwards only the env vars you list in TERMINAL_CODER_FORWARD_ENV.
From the plugin's catalog listing.
How to install
Install it. Hermes asks for any API keys it needs (this one needs CODER_URL, CODER_API_KEY, CODER_WORKSPACE), then asks whether to turn it on.
hermes plugins install coder
Said no? Turn it on later:
hermes plugins enable coder
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Freight Reconciliation
Community
Payer-side freight reconciliation: import carrier bills and trip ledgers into a deterministic local core (SQLite, WAL, no cloud), re-calculate against contracted rates and produce evidence-linked difference lists for…
Payer-side freight reconciliation: import carrier bills and trip ledgers into a deterministic local core (SQLite, WAL, no cloud), re-calculate against contracted rates and produce evidence-linked difference lists for human review — 14 MCP tools over uvx stdio (engine pinned to the immutable commit e8cd259c, release v0.4.1), with 3 bilingual workflow skills bundled. Portable Agent Plugins v1 package (mcp.json + skills/); needs uv on PATH. Never approves payments, sends messages or writes back to ERP/TMS; final confirmations route through a local admin page the model cannot reach.
Good to know before installing
The optional freight-admin page listens on 127.0.0.1 and is where a human confirms mappings, rules, matches and exports; nothing leaves the machine.
From the plugin's 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 freight-reconciliation
Said no? Turn it on later:
hermes plugins enable freight-reconciliation
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).
Auto fetch/pull before reads, and commit + push only the files each turn changed, for every git worktree Hermes touches.
Good to know before installing
After each turn it commits and pushes (push on by default; GIT_HOOK_PUSH=0 keeps commits local) the changed files of git worktrees under GIT_HOOK_ROOTS (default PROJECTS_ROOT, "*" for every repo), pushing to origin HEAD when no upstream is set; it pulls --ff-only before reads. A branch whose direct push the remote refuses on policy grounds (branch protection, a PR-required ruleset) is never committed to again: the hook drops its own unpushed commit, leaves the edit staged and dirty, and reports it once.
From the plugin's 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 git-hook
Said no? Turn it on later:
hermes plugins enable git-hook
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).
Bounded tools to list, read, create, and control local T3 coding threads on Linux and WSL2.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install hermes-t3-control
Said no? Turn it on later:
hermes plugins enable hermes-t3-control
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).
Central Hermes Desktop inbox for reports produced by local cron runs.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install cron-bulletin
Said no? Turn it on later:
hermes plugins enable cron-bulletin
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).
Agent Plugins v1 package: one skill plus one stdio MCP server (mcp_select) started with uv run from the checkout. Needs uv on PATH. Registers no Hermes tools or hooks; do not expect jev_* tools.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install jev-mcp-router
Said no? Turn it on later:
hermes plugins enable jev-mcp-router
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).
Local-first diagnostics, safety audit, and incident postmortems for Hermes Agent.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install doctorpack
Said no? Turn it on later:
hermes plugins enable doctorpack
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).
NetBox change management: query DCIM/IPAM objects, build a reviewed field-level diff, apply with a journal and roll back.
How to install
Install it. Hermes asks for any API keys it needs (this one needs NETBOX_URL, NETBOX_TOKEN), then asks whether to turn it on.
hermes plugins install hermes-plugin-netbox
Said no? Turn it on later:
hermes plugins enable hermes-plugin-netbox
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).
Typed adapter for the reproducible JACKAL v1.7.3 release: 41 catalog-derived verification tools (exact, numerical, Lean-checked bounded lanes, claim replay).
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install jackal-verified
Said no? Turn it on later:
hermes plugins enable jackal-verified
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).
Agent Plugins v1 package: one skill plus one stdio MCP server (skill_select) started with uv run from the checkout. Needs uv on PATH. Suggests at most one skill per request via the TypeSafe (Jev) cookbook pattern; roster is read live from the profile skills dir. Note: the portable loader does not interpolate env in mcp.json — JEV_TYPESAFE_API_KEY must be present in the server's inherited environment (native mcp_servers declaration works too).
How to install
Install it. Hermes asks for any API keys it needs (this one needs JEV_TYPESAFE_API_KEY), then asks whether to turn it on.
hermes plugins install jev-skill-router-mcp
Said no? Turn it on later:
hermes plugins enable jev-skill-router-mcp
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Turn Usage
Community
Usage and cost footer appended to every reply — tokens, cache hit rate, cost and context occupancy, plus a per-tool time breakdown showing which tool actually consumed the wall clock.
Usage and cost footer appended to every reply — tokens, cache hit rate, cost and context occupancy, plus a per-tool time breakdown showing which tool actually consumed the wall clock. Waiting time (a blocking user prompt) is reported separately and excluded from the active-time denominator. Pure computation, never calls a model; any failure leaves the reply untouched.
Good to know before installing
The usage footer is appended to the stored assistant reply, so it is replayed to the model on later turns and adds tokens to every turn.
From the plugin's 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 turn-usage
Said no? Turn it on later:
hermes plugins enable turn-usage
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).
Desktop and dashboard plugin: statusbar chip, palette command, and dashboard tab listing your GitHub repos (public + private) via the gh CLI.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install my-github
Said no? Turn it on later:
hermes plugins enable my-github
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Completion Sound
Community
Pick the sound Hermes Desktop plays when a turn finishes: one of the 14 built-in presets or your own audio file (mp3, wav, ogg), with an optional different sound during night hours.
Pick the sound Hermes Desktop plays when a turn finishes: one of the 14 built-in presets or your own audio file (mp3, wav, ogg), with an optional different sound during night hours. Files stay in the plugin's local storage. Desktop-only (desktop/plugin.js inside the plugin SDK surface); no agent tools, hooks, middleware or env vars.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install completion-sound
Said no? Turn it on later:
hermes plugins enable completion-sound
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Cua Spaces
Verified
Cua's own plugin: runs Hermes's terminal, file and code tools inside a Cua Space, an isolated Linux, macOS or Windows machine you can watch live, as a terminal backend (`hermes config set terminal.backend cua`).
Cua's own plugin: runs Hermes's terminal, file and code tools inside a Cua Space, an isolated Linux, macOS or Windows machine you can watch live, as a terminal backend (`hermes config set terminal.backend cua`). On Hermes 0.22.3 and later, Bot Desktop, computer_use and the browser follow the terminal into the Space too (needs the `cua` command).
Good to know before installing
Installs the `cua` Python SDK (>=0.5.0,<0.8); every command the agent runs, every file it touches, and (on 0.22.3+) every screen, click and page the agent drives go to the Space: on this machine for a local Space, or on Cua's cloud (cua.ai) or a machine you name, using the sign-in `cua auth login` saved (the plugin never reads or stores a token, and keeps CUA_API_KEY/CUA_DAEMON_TOKEN out of the Space). Windows Spaces run Hermes's tools in Git Bash, like Hermes on a Windows PC: if the Space lacks Git for Windows or Python, the plugin installs them inside the Space (pinned official installers checked against SHA-256, `winget` fallback) and adds `C:\c`-style drive aliases there. The optional `desktop` setting installs a desktop stack (VNC, Chromium, agent-browser, cua-driver) inside a Linux Space with sudo there. Nothing is installed on this machine. With the default `space: create` it makes a fresh Space per session and deletes it when Hermes finishes (`delete_on_exit`); because that Space is a disposable sandbox, Hermes skips its dangerous-command prompts there, as it does for its other container backends. A Space you name is never deleted and keeps the prompts.
From the plugin's 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 cua-spaces
Said no? Turn it on later:
hermes plugins enable cua-spaces
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).
Directory-scoped session tabs across the terminal.
Good to know before installing
Requires OS-installed tmux; starts private, long-running tmux/Hermes clients only when invoked. Stores non-secret workspace metadata in profile plugin-data, filters child environments, and confirms closes. Does not patch Hermes or read conversations/credentials.
From the plugin's 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 cli-session-tabs
Said no? Turn it on later:
hermes plugins enable cli-session-tabs
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).
Git publishing and independent cloning using local Nostr keys and Hashtree. Instruction-only skill; requires separately installed htree and git-remote-htree, invokes shell commands, and can publish repository history.
Good to know before installing
Instruction-only skill: the agent runs git, htree and git-remote-htree in the terminal (installed separately by the user, or by the agent from the project's release binaries or an unpinned `cargo install hashtree-cli git-remote-htree`); a push publishes the repository's history and author metadata to Hashtree storage servers and Nostr relays, publicly unless a link-visible or private URL is used; the CLI creates and stores a local signing key, and an optional htree daemon keeps running until stopped.
From the plugin's 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 hashtree-git
Said no? Turn it on later:
hermes plugins enable hashtree-git
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Hermes Themes Pack
Community
The 23 Omarchy stock themes (Tokyo Night, Catppuccin, Gruvbox, Nord, Rose Pine, Jade Horse and more) as Hermes skins, with one /theme command that switches the CLI, the TUI and Desktop together.
The 23 Omarchy stock themes (Tokyo Night, Catppuccin, Gruvbox, Nord, Rose Pine, Jade Horse and more) as Hermes skins, with one /theme command that switches the CLI, the TUI and Desktop together. Optionally follows the Omarchy theme. Works without Omarchy.
Good to know before installing
Registers only the /theme command (plus a `hermes theme` CLI subcommand under plugins.isolation: in_process); nothing runs at load time. /theme writes the pack's skins and a receipt under the active profile's HERMES_HOME (personal or edited skins of the same name are skipped) and selects one by running `hermes config set display.skin <name>`; it never edits config.yaml itself. It reads the current Omarchy theme from ~/.local/state/omarchy/current/theme.name. Only after /theme follow on does it write one executable hook into $XDG_CONFIG_HOME/omarchy/hooks/theme-set.d/; Omarchy runs it on theme switches and it switches ~/.hermes and every profile under ~/.hermes/profiles that has the pack installed. No network calls, background processes, Hermes tools, hooks or middleware, credentials, telemetry or self-updater.
From the plugin's 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-themes-pack
Said no? Turn it on later:
hermes plugins enable hermes-themes-pack
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).
Private mesh networking through the separately installed nvpn CLI. Instruction-only skill; connects to relays and peers and starts a persistent daemon. Tunnels need elevated host networking privileges.
Good to know before installing
Instruction-only skill: the agent runs the separately installed nvpn CLI in the terminal (installed by the user, or by the agent from the project's latest GitHub release or an unpinned `cargo install nvpn`), which creates local device keys, connects to Nostr relays and peers, starts a persistent daemon that with elevated privileges creates tunnel interfaces and routes, and on an admin host can approve devices into the user's private network.
From the plugin's 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 nostr-vpn
Said no? Turn it on later:
hermes plugins enable nostr-vpn
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Smol machines
Community
smol machines' own plugin: runs Hermes's terminal, file and code tools in a smol machine, a microVM with its own Linux kernel on this computer (macOS on Apple Silicon, or Linux with KVM), as a terminal backend…
smol machines' own plugin: runs Hermes's terminal, file and code tools in a smol machine, a microVM with its own Linux kernel on this computer (macOS on Apple Silicon, or Linux with KVM), as a terminal backend (`hermes config set terminal.backend smolmachines`). It needs no Docker and no account.
Good to know before installing
Installs the `smolmachines` Python SDK (>=1.27.2,<2), which carries the VM engine. Everything runs on this computer: the plugin always asks the SDK for a local machine, so nothing is sent to smol machines' cloud, even with SMOL_CLOUD_TOKEN set or the smol CLI signed in (Hermes strips SMOL_CLOUD_TOKEN from the commands it runs). Creating a machine pulls its image (default `python:3.12-slim`, from Docker Hub), and the engine pulls with this computer's Docker registry login when one is configured (`~/.docker/config.json`, including a credential helper such as the macOS keychain), read-only and sent only to the registry being pulled from. A machine has outbound network access and mounts nothing from this computer. With `terminal.container_persistent` (the Hermes default) each Hermes home and session keeps one machine, which keeps running after Hermes exits until stopped or deleted with the smolvm CLI, otherwise the machine is deleted when the session ends. Because the machine is a disposable sandbox, Hermes skips its dangerous-command prompts there, as it does for its other container backends.
From the plugin's 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 smolmachines
Said no? Turn it on later:
hermes plugins enable smolmachines
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
No plugins match that search.
Read before you install
Plugins run code inside your agent. Official plugins come from Nous Research's own repo. Community plugins are independent projects, so check the source, the permissions they ask for and any API keys they need. New to plugins? Start with skills vs plugins vs MCP.
