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.
880 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.
ree_validate_receipt, ree_verify_receipt, ree_infer. Validate does not re-execute and does not stand behind text_output, finish_reason, token_count, model.name, or ree_version. Verify re-executes on CPU. Infer runs one of three small models and writes one receipt.
Good to know before installing
Starts containers from the local image gensynai/ree:v0.8.0 (pinned by digest) and never pulls it; running docker pull yourself is consent to the REE-Binary-License. ree_verify_receipt and ree_infer mount ~/.cache/gensyn and ~/.cache/huggingface read-write (a Hugging Face token file stored there is visible to the container; no token is passed in the environment), may download Hugging Face weights for any model a receipt names, and their container network is not limited to Hugging Face; they ask for Hermes approval on every call and refuse under cron, yolo, approvals off, single-query, unattended runs, host isolation, or when the approval API is missing. ree_validate_receipt runs with network none, does not ask, and returns no receipt text. Any person admitted to one of your gateways can call these tools and approve containers on your Docker daemon; disable per surface with hermes tools. Choosing "always" adds one config.yaml allowlist line per call and never covers the next call. New receipts and temporary work files are written under ~/.cache/hermes-ree; nothing is stored under HERMES_HOME. The container is not a hostile-code sandbox. No cron is created.
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-gensyn-ree
Said no? Turn it on later:
hermes plugins enable hermes-gensyn-ree
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).
Read-only dashboard tab and model-free /duty and hermes duty summaries for waiting conversations, unanswered messages, running turns, undelivered background results and failing cron jobs. Supports all 17 dashboard languages, including right-to-left Arabic.
Good to know before installing
Opens HERMES_HOME/state.db with SQLite mode=ro (sessions, messages, turn leases, async delegations, goals) and reads cron/jobs.json and gateway_state.json; writes only HERMES_HOME/duty-board/dismissed.json for dashboard dismissals. Chat requires in-process Hermes 0.21.7+ and a configured owner; shared-chat summaries default to counts only. No network calls, no model calls, no credentials, no background processes.
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 duty-board
Said no? Turn it on later:
hermes plugins enable duty-board
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).
Nous Portal usage widget for the Hermes desktop statusbar — remaining credits plus plan-usage percentage, with portal detail on hover.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install billing
Said no? Turn it on later:
hermes plugins enable billing
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).
Approval-gated local security audit for Hermes Agent using Gitleaks, OSV-Scanner, and Semgrep CE.
How to install
Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install hermes-security-audit
Said no? Turn it on later:
hermes plugins enable hermes-security-audit
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).
Live, now-centered Gantt timeline for the Hermes kanban boards — a slidable, persisted 72 h window (default now -24h -> now +48h; drag to move, drag the ends to resize), free wheel zoom down to hour ticks, a now line, status filtering, an optional done lane, and lifecycle rendering (dashed waiting vs solid run spans at real durations). Fork of kanban-gantt (GPL-3.0).
Good to know before installing
The backend can transition, reassign, comment on and permanently delete kanban tasks on any board (Desktop asks for confirmation before deletes); local SQLite only, no 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 kanban-live-gantt
Said no? Turn it on later:
hermes plugins enable kanban-live-gantt
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).
Provider-native Claude and Codex remaining allowance windows in the Hermes Desktop status bar.
Good to know before installing
Spawns the local `codex app-server` and `claude auth status` CLIs and reads the Claude OAuth token read-only through Hermes core; the optional install.sh (not part of the catalog install) edits the statusLine in ~/.claude/settings.json; 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 model-usage-status
Said no? Turn it on later:
hermes plugins enable model-usage-status
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.
Kuma
Community
Uptime-Kuma monitoring for agents: the community MCP server for Uptime Kuma v2 (pinned @0.11.18 over npx stdio) with workflow skills for incident review, status digests, and confirmation-gated maintenance.
Uptime-Kuma monitoring for agents: the community MCP server for Uptime Kuma v2 (pinned @0.11.18 over npx stdio) with workflow skills for incident review, status digests, and confirmation-gated maintenance. Credentials stay in host-native MCP config (portable Agent Plugins v1 package, mcp.json + skills/; needs Node.js >= 22 on PATH and a Uptime Kuma v2 instance).
Good to know before installing
First run has npx fetch @davidfuchs/mcp-uptime-kuma@0.11.18 (single-maintainer community package) from npm; that server exposes 31 read/WRITE tools against your Uptime Kuma instance, including permanent delete tools the bundled skills never 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 kuma
Said no? Turn it on later:
hermes plugins enable kuma
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.
Iowap
Community
Fleet control for Hermes Desktop: live statusbar chip (N/M IOWAP nodes online), a draggable fleet pane, a full fleet page (status, load, queue depth, capabilities per node, activity) and a tasks page that submits to…
Fleet control for Hermes Desktop: live statusbar chip (N/M IOWAP nodes online), a draggable fleet pane, a full fleet page (status, load, queue depth, capabilities per node, activity) and a tasks page that submits to any task-type capability on the fleet and tracks submitted tasks live (per-stage status dots, result previews, artifacts). Data stays local via the local node-cli against your own IOWAP relay; agent sessions join through an optional iowap-task bridge into a shared track store.
Good to know before installing
The dashboard backend runs the local node-cli (the IOWAP node client from github.com/iowap-org/iowap-node) to read your relay's node list, capabilities and task results, and to submit tasks you start from the Tasks page to nodes on your IOWAP fleet. Relay health also goes through the local node-cli (`server health`) — the plugin itself makes no raw HTTP calls to the relay; node identity comes from the node's own ~/.relay state files. Tracked task ids are stored in your Hermes home under plugin-data/iowap/.
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 iowap
Said no? Turn it on later:
hermes plugins enable iowap
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).
Session command tray — shell commands the Hermes agent ran via the terminal tool (success and failure). Desktop pane and /commands. No API keys.
Good to know before installing
Records terminal commands with exit code, workdir and a 160-char redacted output preview to $HERMES_HOME/plugin-data/command-tray/state.json; the Desktop pane inserts text through Hermes Desktop's internal hermes:composer-insert event (not a public SDK API) with clipboard fallback; no 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 command-tray
Said no? Turn it on later:
hermes plugins enable command-tray
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).
Native Hermes Agent plugin that runs the local Atoll notch monitor for Hermes session and turn status on macOS.
Good to know before installing
MacOS only. Starts a detached Node daemon on every Hermes session that reads state.db read-only and sends session titles, model/profile/token stats and a ≤96-char redacted preview of your latest request to the third-party Atoll notch app over localhost. hermes notch setup clones and builds the author's Atoll fork (github.com/himanusia/Atoll at a pinned commit, not reviewed here) with Xcode and installs an unnotarized app to ~/Applications. Node deps install via Hermes's npm ci prompt. Run hermes notch stop before removing.
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-atoll
Said no? Turn it on later:
hermes plugins enable hermes-atoll
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
Off-Peak Watch (offpeak-bekci)
Community
Makes Ollama Cloud's off-peak window visible and actionable in Hermes: a desktop status-bar chip shows the countdown and the queue item counts (Ollama off-peak hours: weekdays 18:00-12:00 UTC, weekends one block), a…
Makes Ollama Cloud's off-peak window visible and actionable in Hermes: a desktop status-bar chip shows the countdown and the queue item counts (Ollama off-peak hours: weekdays 18:00-12:00 UTC, weekends one block), a one-shot notice fires 30 minutes before the window opens, and approval is taken only from the user (`/offpeak-onayla <id,id>`) — work runs only if approved, and items never enter the queue by themselves. `/offpeak-durum` prints a readable report by default (machine-readable JSON with `/offpeak-durum json`), and `/offpeak-kur` prints the cron job it would install in full plus a `plan_hash`; nothing is installed without a hash-bound approval typed by the user, and the plugin never writes the cron store. One `llm_execution` middleware measures the call rate for Ollama Cloud calls during the peak window and ships measure-only (`kuru_kosu: true`): it records what it would delay and never delays. No network calls, no telemetry, no credential reads; the only local files it touches are the queue ledger, its own JSONL measurement log, and a read-only look at the profile's cron/jobs.json. Output language is English by default; `dil: tr` selects Turkish. Auto-delivery is host-dependent: in a classic CLI session the request enters the agent queue; on the Ink TUI / desktop-panel host the core asks for a persistent `session_key`, which the command handler does not receive, so the command prints the parameters as a single line of JSON. Injecting into a gateway additionally requires `plugins.entries.offpeak-bekci.allow_gateway_injection: true` (default off); the only in-process way to read that key is the private `gateway.session_context` module (rule 9 -> not used). Requires Hermes >= 0.22.2.
Good to know before installing
The llm_execution middleware can sleep Ollama Cloud calls during the peak window once `kuru_kosu: false` is set (default is measure-only); it writes a JSONL measurement log and, on `/offpeak-onayla`, rewrites the user's queue file; it reads the profile's cron/jobs.json read-only (on `/offpeak-durum`, `/offpeak-kaldir` and at every session end) to count enabled queue-consumer jobs; `/offpeak-kur` and `/offpeak-kaldir` leave cron install/removal requests in the session (or, with `allow_gateway_injection: true`, inject them into the gateway) for the agent's own cron tool to act on; no network calls, no credential reads, never writes the cron store.
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 offpeak-bekci
Said no? Turn it on later:
hermes plugins enable offpeak-bekci
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).
Multi-repo GitHub issues & PRs in an Orca-style Tasks view for Hermes Desktop.
Good to know before installing
Uses your logged-in `gh` CLI and `git` through Hermes Desktop's shell bridge, or a GitHub token you paste in the panel (stored unencrypted in Desktop plugin storage, sent only to api.github.com); scans your configured clone folders for GitHub repos and reads skill names under ~/.hermes; polls the active-session list of every Hermes profile every 10 seconds for status chips; approve, close, reopen, comment and merge act on GitHub from the panel; creates git worktrees and opens Hermes sessions seeded with the issue/PR title and body as fenced untrusted text, and without a shell bridge asks the agent to run the worktree git commands.
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-tasks
Said no? Turn it on later:
hermes plugins enable git-tasks
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).
Everything that snagged - cross-session shelf of failed tool calls. Full Desktop page, chip, pin, fix-prompt insert. No API keys.
Good to know before installing
Stores failed tool-call metadata (tool, truncated args with key-name redaction, error snippet) locally in plugin-data; no 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 snag-shelf
Said no? Turn it on later:
hermes plugins enable snag-shelf
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).
Store a secret on the gateway host without showing it to the model.
Good to know before installing
Stores the value in plaintext in the profile .env (mode 0600) and adds the name to terminal.env_passthrough, so $NAME is available to the terminal tool; the model can still read the value with its own tools (cat .env, echo $NAME). Keeps secrets out of chat/prompt context and redacts verbatim output of credential-shaped values; it is not a boundary against a model that deliberately reads it. Adds a static system-prompt section and a /secret command. Imports private core helpers read-only (_config_profile_scope, _is_hermes_provider_credential, _CONFIG_LOCK).
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 secret-drop
Said no? Turn it on later:
hermes plugins enable secret-drop
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.
Alan's Way Plugin: Computer Use
Community
Computer-use provider for Hermes: the stock computer_use tool drives desktop apps on the user's computer through the Alan's Workspace app, and on the VM's own desktop when the computer is offline.
Computer-use provider for Hermes: the stock computer_use tool drives desktop apps on the user's computer through the Alan's Workspace app, and on the VM's own desktop when the computer is offline. Needs the Alan's Way Plugin's workspace setup. Select it with computer_use.backend: alans-way-computer (the Alan's Way Plugin's setup.sh sets this when it installs the provider; in the catalog flow it prints the command).
Good to know before installing
Starts the workspace router from the profile's mcp_servers.workspace_browser block (command and args from config.yaml, with a filtered environment plus HERMES_WORKSPACE_ALLOW_DESKTOP_ACTIONS=1, which lets this private router child serve desktop input) as a long-running node child per session. The filtered environment passes PATH, HOME, locale and OS basics, plus DISPLAY, XAUTHORITY and DBUS_SESSION_BUS_ADDRESS so the router's VM-desktop fallback finds the X display and session bus, plus HERMES_HOME set to the bound profile's home, under which the router appends a content-free serving log to logs/workspace-router.log; no keys or tokens. It talks to the router over stdio (app lists, element trees, screenshots and input actions). The router reaches the user's computer over SSH on the user's tailnet and falls back to the VM's desktop, where it uses xdotool, a screenshot tool and the AT-SPI accessibility bus if they are installed (the provider installs none of them). On the user's Mac the provider can bring the target app to the front when the model asks for it (focus_app with raise_window, or an input action with delivery_mode foreground), and the Alan's Workspace host does so only aft
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 alans-way-computer
Said no? Turn it on later:
hermes plugins enable alans-way-computer
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).
Jev-powered Hermes plugin for skill/model routing, typed assess, DOM/Cua computer use, adaptive reasoning effort with a per-turn receipt line, and FTS rerank.
Good to know before installing
The default-on adaptive llm_request sends up to 1,200 characters of the current user message to TypeSafe/OpenRouter after Hermes redact_for_egress (no history or tool output); greetings and thanks are decided locally with no call; without the Hermes redactor it sends metadata only (disable via adaptive_reasoning_effort false). Separate default-on hosted skill routing sends up to 4,000 characters of the current user turn after Hermes redact_for_egress, plus skill names, to the same provider; without the redactor it stays local (opt down to local_only); light turns (greetings, closed acknowledgements, and read-only listings) skip that hosted call by default. Model routing remains advisory. Disclosure — By default, adaptive effort sends up to 1,200 characters of the current user message, and hosted skill routing sends up to 4,000 characters plus skill names, to TypeSafe/OpenRouter Jev after Hermes redact_for_egress (greetings and light turns stay local). The jev_session_search_rerank and jev_computer_use DOM tools send query/card and public-page text using the plugin's own masking. Off unless enabled: evidence prefetch sends source files the user names under evidence_finder_root (up t
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-switchyard
Said no? Turn it on later:
hermes plugins enable hermes-switchyard
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).
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.
Severian
Community
Local-first long-term memory for Hermes agents: a canonical append-only store (SQLite or PostgreSQL+pgvector) with five-dimensional tenant/profile/collection/agent/session scope, hybrid BM25+vector retrieval…
Local-first long-term memory for Hermes agents: a canonical append-only store (SQLite or PostgreSQL+pgvector) with five-dimensional tenant/profile/collection/agent/session scope, hybrid BM25+vector retrieval with a re-ranker, memories that cite the observations they came from, per-turn user facts, real dates next to relative times, truth resolution when a newer fact replaces an older one, and a conflict note when two returned memories disagree. Fully offline by default; Qwen3-Embedding-0.6B semantic embeddings opt-in, locally or in a user-owned sidecar. On OmniMemEval's public long-term-memory leaderboard (its own models, prompts and full public sets) it scores 90.6 LongMemEval (1st), 87.3 LoCoMo (2nd) and 71.6 BEAM 100K (2nd, within noise of the lead); it re-ran LCM-X to check the board's records, and per-question results, a strict second marker and scripts are published in the repo.
Good to know before installing
Stores every conversation turn in one SQLite database under the Hermes root (`<hermes root>/severian`) shared by all profiles with rows scoped per profile, or in the PostgreSQL database named by `SEVERIAN_DSN`; the opt-in Qwen/Granite embeddings download a model from Hugging Face on first use, and the opt-in embedding sidecar sends memory text to the URL you configure.
From the plugin's catalog listing.
How to install
Install it. Hermes asks for any API keys it needs (this one needs SEVERIAN_DSN), then asks whether to turn it on.
hermes plugins install severian
Said no? Turn it on later:
hermes plugins enable severian
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).
Guided Aixy inference setup with optional MCP tools: hermes aixy setup selects an available model or route, and hermes aixy mcp connects tools later. MCP is skipped by default.
Good to know before installing
Exposes CLI commands only, with no automatic hooks or runtime tools. Explicit inference setup sends the project key in an authenticated GET /models to the configured Aixy gateway (https://api.aixy-gateway.com/v1 by default), rejects redirects, and asks before updating the selected Hermes profile's provider and main model settings. The key is stored through Hermes' credential writer as AIXY_API_KEY; provider settings contain a variable reference. Model requests send Hermes' opaque conversation scope in X-Aixy-Session-ID for grouping in Aixy Activity. No inference requests are sent during setup. Optional MCP setup starts the installed Hermes CLI as a child process for browser OAuth, credential storage and tool selection against the independent MCP endpoint (https://api.aixy-gateway.com/mcp by default). The child uses the selected profile, disables inherited unattended and YOLO flags, and receives no key in command arguments. Setup requires an interactive terminal. No additional dependencies, telemetry, persistent background processes 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 aixy
Said no? Turn it on later:
hermes plugins enable aixy
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).
Delete and package skills, browse their markdown files, and save per-profile on/off presets from one Settings page.
Good to know before installing
Deleting a skill from its page moves the skill folder out of `<HERMES_HOME>/skills` (on Windows to the Recycle Bin by running `powershell.exe`, elsewhere to `<HERMES_HOME>/better-capabilities-trash/`); applying a preset switches skills, toolsets and agent plugins on or off, including for other profiles the preset names.
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 better-capabilities
Said no? Turn it on later:
hermes plugins enable better-capabilities
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).
Clinician decision-support calculators, not a regulator-reviewed medical device; runs fully offline with no network calls, stores only your favourites list in Desktop plugin storage, Copy puts the result on the system clipboard, and source citations open in your browser when clicked.
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 canadian-primary-care
Said no? Turn it on later:
hermes plugins enable canadian-primary-care
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.
Plugin Catalog (Italian)
Community
The official Hermes plugin catalog in a native page (sidebar entry, route /catalogo, plus a command-palette entry) with an Italian interface and on-the-fly Italian descriptions: Google Translate first, MyMemory…
The official Hermes plugin catalog in a native page (sidebar entry, route /catalogo, plus a command-palette entry) with an Italian interface and on-the-fly Italian descriptions: Google Translate first, MyMemory as a second public source, and a final fallback to the user's own local llama.cpp model.
Good to know before installing
It fetches the public catalog feed (hermes-agent.nousresearch.com) and, when you open a plugin entry, sends that entry's English description to translate.googleapis.com (Google Translate's keyless public endpoint) and, if that fails, to api.mymemory.translated.net; nothing else leaves the machine. It reads no credentials or Hermes files, and its backend route is empty. Translation runs when a plugin entry is opened, not for the whole catalog. No telemetry. UI is Italian-first with an English bundle.
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 catalogo-it
Said no? Turn it on later:
hermes plugins enable catalogo-it
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).
Conservative Chrome tab cleanup with in-process observation and browser-call leases.
Good to know before installing
Runs a background thread inside Hermes that proxies your local Chrome DevTools port (127.0.0.1:9222 → 127.0.0.1:9223, loopback only, you must point browser.cdp_url at it), injects a focus/activity listener into every Chrome page, rewrites browser_exec session names to a per-profile namespace, and a cron script you schedule auto-closes idle, duplicate and blank tabs (including tabs with unsaved text).
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 chrome-tab-watchdog
Said no? Turn it on later:
hermes plugins enable chrome-tab-watchdog
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).
Full setup steps, settings and screenshots are on the plugin's official catalog page from Nous Research.
CloudGPU
Community
cloudgpu.app models (DeepSeek, Kimi, GLM, MiniMax) via the OpenAI-compatible API at cloudgpu.app/v1: live model list from the public /v1/models, DeepSeek V4.1 Flash as the default.
cloudgpu.app models (DeepSeek, Kimi, GLM, MiniMax) via the OpenAI-compatible API at cloudgpu.app/v1: live model list from the public /v1/models, DeepSeek V4.1 Flash as the default.
Good to know before installing
Model provider; prompts, tool schemas and CLOUDGPU_API_KEY go to cloudgpu.app (or to CLOUDGPU_BASE_URL when the user sets it).
From the plugin's catalog listing.
How to install
Install it. Hermes asks for any API keys it needs (this one needs CLOUDGPU_API_KEY), then asks whether to turn it on.
hermes plugins install cloudgpu-provider
Said no? Turn it on later:
hermes plugins enable cloudgpu-provider
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.
