ProofOps

From its catalog listing

Verification for AI agent completion claims: turn "the agent said done" into a sealed receipt of what was checked, what was observed, and what passing does NOT prove. Hermes runs a declared plan of read-only checks against a live service, a deliverable or a system of record, and gets a receipt: each check's actual result, what it proves, and - printed on every receipt - what passing does NOT prove. Fourteen check types: HTTP status/JSON/body/headers, command exit codes, file and directory inventory, checksums, CSV shape, image dimensions, PDF pages/size/text, and read-only SQLite queries. Receipts are sealed with a sha256 digest and can be HMAC-signed, so editing a verdict after the run is detectable; `verify` reports valid / tampered / unsealed / needs-key. A check that could not run is reported NOT RUN - never a green tick - and the receipt carries claimable: false. Refuses undeclared origins, undeclared commands, unknown check types, and paths outside the operator's allowed_paths.

Good to know before installing

network: HTTP GET only, against origins the plan names, resolving each host once and connecting only to the addresses it classified (every redirect hop too), refusing loopback/private/link-local addresses unless the operator allows local targets, environment proxies ignored; shell: exactly the argv a plan lists, and only when the operator also lists that command verbatim in plugins.entries.proofops.settings.allowed_commands - there is no approval prompt inside a tool call, because there is nobody to answer one; reads: no file or SQLite access at all until the operator sets plugins.entries.proofops.settings.allowed_paths (an unset fence is a denial, not a default), then only inside the operator's roots and the plan's, SQLite opened read-only and single-statement; storage: receipts under the plugin's own data directory containing observed values, hostname, cwd and command output; credentials: none read or stored, signing is CLI-only; no telemetry by default and no network access at import or registration; telemetry exists only as an explicit opt-in: a one-time "Send anonymous diagnostics" checkbox after the first run, framed as the feedback that decides what gets fixed next, where Enter leaves it unchecked and the refusal is remembered and the exact bytes printable via `proofops share --dry-run` sending an anonymous six-field aggregate (random install id, version, platform, run and plan counts, pass/fail/not-run counts) that `proofops share --dry-run` prints in full beforehand, with version and platform allow-listed on both client and server so no name, path or hostname can be stored; the aggregate carries pass/fail/not-run totals plus the same totals per check type from a closed set of fourteen, so the report can say what kind of thing is verified (web service, file, PDF, database) without saying whose, and is published at https://rasrobo.github.io/proofops/metrics/ Disclosure — network: HTTP GET only, to origins the plan names, connecting only to addresses it resolved and classified (every redirect hop too, proxies ignored) and refusing loopback/private/link-local/CGNAT and other non-global addresses unless the operator sets allow_local_targets; shell: only a command the plan lists verbatim AND the operator lists in plugins.entries.proofops.settings.allowed_commands, run without a shell and with PATH/HOME/LANG plus operator-listed env vars; reads: no file or SQLite access until the operator sets plugins.entries.proofops.settings.allowed_paths, then only inside those roots, SQLite read-only; storage: receipts under the plugin's data directory, containing observed values, hostname, cwd and command output; credentials: none read, signing is CLI-only; telemetry: none from the Hermes plugin, the standalone `proofops` CLI can send an opt-in anonymous aggregate to t.sqs.chat after a one-time prompt.

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 proofops
  2. Said no? Turn it on later:
    hermes plugins enable proofops
  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
rasrobo (Community)
Needs
No API keys declared
Adds tools
proofops_plans proofops_run proofops_receipt proofops_verify
Works on
linux, macos
Needs Hermes
0.21.5 or newer
Version
0.6.0
In the catalog
2026-11-11
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