Plugin X-Ray

From its catalog listing

Sets traps for plugins instead of watching them. hermes xray detonate runs a plugin in a throwaway child process with a fake home full of honeytokens, fuzzes its tools, fires its hooks and replays it at +30 and +90 days to catch time-bombs, then gives a RED/AMBER/GREEN verdict with file:line proof, a per-version behaviour diff and a drafted disclosure line. Opt-in live bait flags any installed plugin that reads a decoy credential file and can route its next tool call to Hermes' approval prompt.

Good to know before installing

spawns child Python processes to detonate plugins; the child runs as you (fake HOME, real keys stripped) and is not an OS sandbox, so its egress and spawn blocking (Python audit hooks, incl. fork and fork_exec) is a tripwire native code can bypass; reads of your real credential stores are refused and make the verdict RED; runs git clone when you detonate a remote repo, including from the dashboard's detonate button; by default (bait_runtime) installs a Python audit hook in the Hermes process that watches for plugins touching bait files or honeytokens; reads installed plugins' source dirs to attribute events; bait plant (opt-in) writes decoy files only into empty default credential paths of the AWS CLI/SDKs, git credential store, ssh and Solana CLI, so those tools use the fake values until bait remove, which deletes only unchanged files it wrote; enforce (off by default) uses pre_tool_call approve; no LLM calls, no telemetry; X-Ray itself never reads real credentials or patches Hermes core.

From its catalog listing.

How to install

  1. Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
    hermes plugins install xray
  2. Said no? Turn it on later:
    hermes plugins enable xray
  3. Restart Hermes so it loads the plugin.

Some plugins also need a sign-in or settings: see Full setup & settings. Memory plugins ask whether to become your memory provider instead. Steps follow the official plugins guide (opens in a new tab).

Category
Coding & developer tools
Maintained by
cipoklean (Community)
Needs
No API keys declared
Adds hooks
on_session_start pre_tool_call
Needs Hermes
0.19 or newer
Version
0.1.0
In the catalog
2026-11-09

Known issues (from its catalog listing)

  • Detonation is not an OS sandbox: the plugin under test really runs in a child process as you and can reach real files by absolute path; only credential-store reads are refused. Detonate unknown code on a machine you don't mind
  • Python audit hooks see Python-level actions only; native code can act below them (any ctypes load is reported). Env-variable theft is caught when the value leaves the process, not when it is read
  • Desktop plugin.js code is not detonated (Python side only)
Using the Hermes desktop app? See where plugins live
Hermes desktop Capabilities page, Plugins tab filtered to Official plugins built by Nous Research, each with an add button.
The official plugin catalog built into the app.Hermes desktop v0.22.5 · Capabilities > Plugins · Windows · captured Nov 1, 2026

Full setup & settings ↗Source code ↗

More in coding & developer tools

All coding & developer tools plugins

New Hermes Agent updates every day on X. Follow @HermesWatcher

← All plugins