All plugins

Official

snyk

Scan code (SAST), dependencies, container images, IaC and SBOMs with Snyk through its first-party MCP server (pinned snyk@1.1306.0 over npx stdio, CLI analytics disabled), with the snyk-security-scan workflow skill bundled. Portable Agent Plugins v1 package (mcp.json + skills/); needs Node.js/npm on PATH and a free Snyk account (browser login via the snyk_auth tool).

NousResearch592ToolsUpdated 25 days ago

About

Scan code (SAST), dependencies, container images, IaC and SBOMs with Snyk through its first-party MCP server (pinned snyk@1.1306.0 over npx stdio, CLI analytics disabled), with the snyk-security-scan workflow skill bundled. Portable Agent Plugins v1 package (mcp.json + skills/); needs Node.js/npm on PATH and a free Snyk account (browser login via the snyk_auth tool).

hermes-plugin-snyk

Part of Hermes Official Plugins, Nous Research's official plugins for Hermes Agent. Formerly NousResearch/hermes-plugin-snyk, which is archived; this directory carries its full history.

Scan code, dependencies, container images, IaC and SBOMs from Hermes Agent
through Snyk's first-party MCP server. Snyk ships the
server inside the Snyk CLI (snyk mcp is a vendor subcommand, not a
community wrapper), so this plugin is a pinned npx stdio launch plus a
workflow skill.

This is a portable Agent Plugins v1 package. One
install ships:

  • mcp.json — the Snyk MCP server entry (sn), registered for every new
    session while the plugin is enabled. No mcp_servers edits in config.yaml.
  • skills/snyk-security-scan/ — the workflow skill: when to use which
    scanner, the auth/trust/scan/fix loop, pitfalls, and a full per-tool
    argument reference generated from the live server.

Install

hermes plugins install snyk       # from the Nous plugin catalog
hermes plugins enable snyk

Then start a new Hermes session. The skill is available as
agent-plugin-snyk-8cb0f11d:snyk-security-scan via skill_view (skills_list
shows the exact name). Node.js/npm must be on PATH (the server is
launched with npx -y snyk@1.1306.0 mcp -t stdio --profile full). The first
launch downloads the pinned CLI.

No credentials are needed at install time. Ask Hermes to run the snyk_auth
tool before the first scan: it opens Snyk's browser login and stores the token
in the Snyk CLI's own config, never in Hermes. A free Snyk account covers the
code (SAST) and open-source (SCA) scanners.

Health check without Hermes:

npx -y snyk@1.1306.0 mcp -t stdio --profile full --DISABLE_ANALYTICS <<'EOF'
{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"probe","version":"0"}}}
EOF

What you get

13 tools, all listed in skills/snyk-security-scan/references/tools.md:
snyk_code_scan (SAST), snyk_sca_scan (dependencies), snyk_container_scan,
snyk_iac_scan, snyk_sbom_scan, snyk_aibom, snyk_package_health_check,
snyk_breakability_check, snyk_auth, snyk_trust, snyk_logout,
snyk_version, snyk_send_feedback.

Hermes exposes them as mcp__agent_plugin_snyk_8cb0f11d__sn__<tool> (the hash
is derived from the install directory name snyk). The
server key is sn rather than snyk because the longest tool name
(snyk_package_health_check) lands exactly on the 64-character function-name
cap of OpenAI-compatible wire formats with a snyk key; sn keeps every
name at 62 or less.

Privacy and telemetry

  • Snyk CLI usage analytics are disabled at launch (--DISABLE_ANALYTICS and
    SNYK_DISABLE_ANALYTICS=1).
  • snyk_send_feedback reports issue-count deltas back to Snyk. The skill
    tells the agent to treat it as opt-in and never call it unprompted.
  • The scans themselves are network calls: SAST uploads source, SCA uploads
    the dependency graph, to Snyk's cloud for analysis. The skill tells the
    agent to ask before scanning private repositories.
  • snyk_trust grants Snyk permission to scan a folder on the user's machine.
    The skill restricts it to the folder the user asked to scan.

Version pinning

mcp.json pins snyk@1.1306.0 (published 2026-07-09). Bumping the pin is a
commit to this repo followed by a reviewed SHA bump in the
hermes-agent plugin catalog.
@latest is deliberately not used.

Attribution

Catalog research, tool pruning rationale and validation originate from
hermes-agent #73860,
re-homed here as a standalone plugin per the hermes-agent policy that
third-party product integrations ship outside the core tree. Snyk and the
Snyk CLI are products of Snyk Ltd. MIT.

README from the reviewed commit abec9e8; it updates when the author re-pins.

More by NousResearch

26 plugins by NousResearch in the catalog.

NousResearchaccent-pickerOKLCH accent colour picker for the Hermes Desktop status bar: drag it and the whole theme retints live, with palette commands to reset to the theme default or copy the current colour. A theme-authoring tool; the colour is scratch state and is never persisted. Desktop-only (desktop/plugin.js inside the plugin SDK surface); no agent tools, hooks, middleware or env vars.OfficialDesktop app592NousResearchadvanced-delegationTwo extra delegation modes for `delegate_task`, next to the built-in default. Model routes (`delegation.backend: model_map`): the agent picks a named model route per subagent from a list you define (e.g. fast, deep, local). Profile routes (`delegation.backend: profile_routes`): the agent runs a subagent as one of your Hermes profiles, with that profile's own model, credentials, skills and SOUL.md. Only route names and their one-line descriptions reach the model. Adds `hermes delegation config` (pick the mode and edit its routes; `--show` prints the setup) and the `/delegation` slash command (save a mode for the next session, or `--now` to apply it to the current chat). Needs Hermes 0.22.5 or newer, the first release with pluggable delegation providers; Hermes 0.22.0 to 0.22.4 refuses to install it, and on a core older than 0.22.0 it installs, logs one warning and does nothing. Disclosure — no Python dependencies and no network or model calls of its own; subagents run through core's `delegate_task` on the routes you configured. Writes only `delegation.backend` and `delegation.backends.*` (model_map / profile_routes) in the active profile's config.yaml, through core's config writer. A model route's optional `api_key` is stored in config.yaml in plain text (`provider:` keeps keys in .env / auth.json). Listing a profile under profile routes lets this profile's subagents use that profile's credentials, SOUL.md and terminal policy.Officialtools592NousResearchagent-importers`hermes import-agent`: import an OpenClaw (~/.openclaw, or legacy ~/.clawdbot / ~/.moltbot), Claude Code (~/.claude), Codex CLI (~/.codex), Cursor (~/.cursor), Grok Bot (a self-export the Bot writes from a prompt the importer prints) or OpenBot desktop (its openbot.db) setup into Hermes in one command; always previews first and asks before applying. Claude Code / Codex / Cursor: instructions, Cursor rules and memories become memory entries, Bash permission rules become command allow/deny lists, MCP servers land in config.yaml, skills are copied, and `--sync` re-imports sources that changed. OpenClaw (core's former `hermes claw migrate`; the plugin keeps that spelling, `hermes claw cleanup` and the openclaw-migration skill): persona, memories, skills, model and messaging settings, MCP servers and agent behaviour. Formerly built into Hermes core; `hermes setup` offers to install it when it finds one of these agents, and profiles with a registered sync source are migrated automatically. Disclosure — no Python dependencies, no network calls and no model calls. Claude Code / Codex / Cursor: reads those agents' local config trees (never their credential files; secret-looking MCP env vars and headers are stripped and listed) and writes only into the active profile (memories/MEMORY.md with a backup, config.yaml, skills/ and import-sync.json). OpenClaw: reads the OpenClaw dir (openclaw.json, its .env, workspace files such as SOUL.md / MEMORY.md / USER.md, skills); API keys and bot tokens come over only with --migrate-secrets (allowlisted names, shown in the preview). It writes into the active profile (config.yaml, .env, SOUL.md, memories/, skills/openclaw-imports/, a migration/openclaw/<time>/ report with item backups, and a backups/pre-migration-*.zip restore point), plus a workspace dir only when --workspace-target names one. It runs local pgrep / systemctl / tasklist checks to warn when OpenClaw or a Hermes gateway is still running, and `hermes claw cleanup` renames the OpenClaw dir to *.pre-migration after a confirmation. Grok Bot / OpenBot: instructions become SOUL.md, memories and user facts become memory entries, skills land in skills/<source>-imports/, scheduled routines become paused cron jobs (--activate-routines to start them) and event routines a notes file; credential-looking export keys refuse the file, and secret MCP env vars and headers are stripped and listed. OpenBot's database is opened read-only (or read from a scratch copy that is deleted after the read).Officialtools592NousResearchblenderOfficial Blender Lab MCP server over stdio, pinned to upstream v1.0.3, with a Blender workflow skill. Needs Git and uv; Blender 5.1+ is not needed at install. The skill opens Blender itself when a task needs it and, after you agree, installs Blender and Blender Lab's MCP add-on. First startup downloads Python dependencies; prepare the uv environment before connecting. Disclosure — tools execute arbitrary Python in Blender with your privileges; the skill starts Blender with online access for that session only (your saved preference is unchanged), and the add-on's local server on port 9876 has no password, so any program on this computer can use it while Blender is open; only after you agree does the skill download Blender from download.blender.org (about 400 MB, about 1.5 GB unpacked), check it against blender.org's sha256 list and install it in your own folder without administrator rights (Linux ~/.local/opt, macOS ~/Applications, Windows %LOCALAPPDATA%\Programs\Blender Foundation; never over an existing Blender), and download the v1.0.3 add-on, check its hash and install or enable it; first start downloads the pinned Blender Lab MCP server and its Python dependencies with uv. Server discovery does not prove scene readiness.Officialtools592