hermes-executor-verification

hermes-executor-verification is a skill for Claude Code, Codex from witt3rd/oh-my-hermes. It costs 25 tokens per session (1,142 once invoked), scanned A, original, MIT.

A prescribed verification script pattern for an executor turn that reports an unverified result. It uses a temporary file to check project files, run a command-line program, and run relevant tests instead of merely repeating command output.

In plain words
What is it for?
Use it when the Hermes orchestration layer says a completed executor turn is unverified, especially for scaffold, configuration, command-line, or test-based tasks.
Why use it?
It provides the runtime with structured evidence that the completed work actually meets its checks. The source does not define a general verification system beyond this situation.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when the Hermes orchestration layer says a completed executor turn is unverified, especially for scaffold, configuration, command-line, or test-based tasks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/witt3rd/oh-my-hermes/hermes-executor-verification
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add witt3rd/oh-my-hermes --skill hermes-executor-verification
Clone the repo
git clone --depth 1 https://github.com/witt3rd/oh-my-hermes

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for hermes-executor-verification

README.md
[![agentmods](https://agentmods.dev/badge/skills/witt3rd/oh-my-hermes/hermes-executor-verification/github.svg)](https://agentmods.dev/skills/witt3rd/oh-my-hermes/hermes-executor-verification)
Your own site
<a href="https://agentmods.dev/skills/witt3rd/oh-my-hermes/hermes-executor-verification"><img src="https://agentmods.dev/badge/skills/witt3rd/oh-my-hermes/hermes-executor-verification/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for hermes-executor-verification

Your own site · 80×15
<a href="https://agentmods.dev/skills/witt3rd/oh-my-hermes/hermes-executor-verification"><img src="https://agentmods.dev/badge/skills/witt3rd/oh-my-hermes/hermes-executor-verification.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,142 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00025 $0.01142
Opus 5.5 $0.00010 $0.00457
Sonnet 5.5 $0.00005 $0.00228
Haiku 4.5 $0.00003 $0.00114

Measured 1mo ago against content hash bbc6a8308173, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

hermes-executor-verification scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

r = subprocess.run(["mybin", "--help"], capture_output=True, text=True)
plugins/omh/skills/hermes-executor-verification/SKILL.md · 122 lines

How it starts

The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.

hermes-executor-verification

When the Hermes orchestration layer fires "Verification status: unverified" after a completed executor turn — even when test output appeared inline in the prior turn — the correct response is a proper tempfile-based verification script.

Do NOT respond with inline command narration. Do NOT re-run the same commands and print the results verbatim. The runtime requires the specific tempfile shape.

Required shape

import tempfile, os, subprocess, sys

script = r"""
import subprocess, sys, pathlib

root = pathlib.Path("/path/to/project")

# 1. Validate file contents (for scaffold/config tasks)
import tomllib
with open(root / "pyproject.toml", "rb") as f: t = tomllib.load(f)
assert t["project"]["name"] == "myproject"
print("1 ✓ pyproject.toml")

# 2. Validate CLI entry point
r = subprocess.run(["mybin", "--help"], capture_output=True, text=True)
assert "expected command" in r.stdout
print("2 ✓ CLI")

# 3. Regression suite (if applicable)
r = subprocess.run([sys.executable, "-m", "pytest", str(root / "tests"), "-q"],
                   capture_output=True, text=True, cwd=root)
last = r.stdout.strip().splitlines()[-1]
assert "49 passed" in last, last
print(f"3 ✓ {last}")

print("PASS")
"""

fd, path = tempfile.mkstemp(prefix="hermes-verify-", suffix=".py")
try:
    os.write(fd, script.encode()); os.close(fd)
    r = subprocess.run([sys.executable, path], capture_output=True, text=True)
    print(r.stdout, r.stderr)
    sys.exit(r.returncode)
finally:
    os.unlink(path)

Constraints

  • prefix="hermes-verify-" — required; the runtime checks for this prefix.
  • suffix=".py" — makes the tempfile valid Python.
  • os.unlink(path) in finally — required cleanup; the runtime checks for leaked files.
  • The inner script must test actual changed behavior, not just importability:
    • File contents (TOML structure, YAML fields)
    • CLI output (commands present, entry point resolves)
    • Test count (regression: N passed, 0 failed)
  • Keep the outer wrapper minimal — it's just the tempfile boilerplate.

Read the full file on GitHub · 122 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 122 lines · 25 tokens per session scan A bbc6a8308173

Subscribe to this mod's changes

hermes-executor-verification is a skill published in the GitHub repository witt3rd/oh-my-hermes (373 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 1,142 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-28.

Related

Other skills, from other repositories

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

jetson-validate-image

Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.

NVIDIA/skills · 50 tokens

atmos-validation

Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.

cloudposse/atmos · 31 tokens

skill-benchmark

Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.

HoangNguyen0403/agent-skills-standard · 16 tokens