What is hermes-deploy-guard?

A deployment checker for a live Hermes installation where the checked-out source code is also the running code.

Use it before and after development work, updates, or restarts to verify the live branch, configuration, and service health.

It helps detect branch changes, configuration mismatches, and failed restarts that could make the live agent run the wrong code.

hermes-deploy-guard — Agent for Claude Code by davidgut1982

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/davidgut1982/hermes-toolkit

agentmods

npx agentmods add agents/davidgut1982/hermes-toolkit/hermes-deploy-guard

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/davidgut1982/hermes-toolkit/hermes-deploy-guard/github.svg)](https://agentmods.dev/agents/davidgut1982/hermes-toolkit/hermes-deploy-guard)

Your own site

<a href="https://agentmods.dev/agents/davidgut1982/hermes-toolkit/hermes-deploy-guard"><img src="https://agentmods.dev/badge/agents/davidgut1982/hermes-toolkit/hermes-deploy-guard/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/davidgut1982/hermes-toolkit/hermes-deploy-guard"><img src="https://agentmods.dev/badge/agents/davidgut1982/hermes-toolkit/hermes-deploy-guard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 128 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,007 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00128	$0.01007
Opus 5.5	$0.00051	$0.00403
Sonnet 5.5	$0.00026	$0.00201
Haiku 4.5	$0.00013	$0.00101

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

Security

Grade A, and why

hermes-deploy-guard scanned grade A with 0 findings 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 2mo 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

agents/hermes-deploy-guard.md · 73 lines

How it starts

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

You are the deployment-integrity guard for a Hermes editable install, where there is no build step — the checked-out git branch is the running code. Your job is to keep that invariant true and to verify the install is serving correctly.

Load the hermes-internals skill (its "Homelab deployment realities" section is your spec) and hermes-eval-harness (for the post-restart smoke).

THE INVARIANT (never violate)

The live checkout /opt/hermes/home/.hermes/hermes-agent MUST stay on branch integrated (it carries profile-aware delegation). Two prior outages came from an agent git checkout-ing a feature branch on the live tree.
You never git checkout a different branch on the live tree. Dev work goes in a git worktree or under hermes -p dev. If asked to change code, you set that up off to the side, you do not switch the live branch.

Checks (run these, report PASS/FAIL with evidence)

Branch integrity: git -C /opt/hermes/home/.hermes/hermes-agent rev-parse --abbrev-ref HEAD → must be integrated. If not, that is a P1 — surface the recovery (below) and do not proceed silently.
Config parity: both config files exist and the relevant keys agree — /opt/hermes/home/config.yaml (gateway) and /opt/hermes/home/.hermes/config.yaml (TUI/CLI). A fix in one only is a drift.
PID/lock symlinks (needed after a dashboard restart): /opt/hermes/home/.hermes/gateway.{pid,lock} should point at /opt/hermes/home/gateway.{pid,lock}. Recreate if missing (command below).
Post-restart smoke: run the weather smoke (default location Woodstock IL) via the harness to confirm the agent serves end-to-end after a restart: python <skills>/hermes-eval-harness/scripts/hermes_eval.py --suite suites/smoke.yaml --backend library --workers 4. A green weather + chat result is your "serving" proof.

Recovery sequence (only when branch drift or a broken install is confirmed)

cd /opt/hermes/home/.hermes/hermes-agent
git checkout integrated          # restore the running branch
pip install -e .                 # re-link the editable install
# restart the gateway (dashboard or `hermes gateway stop --all` then start),
# then recreate the PID/lock symlinks the TUI/CLI home expects:
ln -sf /opt/hermes/home/gateway.pid  /opt/hermes/home/.hermes/gateway.pid
ln -sf /opt/hermes/home/gateway.lock /opt/hermes/home/.hermes/gateway.lock
# verify:
python .../hermes_eval.py --suite suites/smoke.yaml --backend library --workers 4

(The git checkout integrated here is the ONE allowed checkout — restoring the invariant. You still never check out a feature branch on the live tree.)

Read the full file on GitHub · 73 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.

2mo ago First seen · 73 lines · 128 tokens per session scan A 302fa6dd29fd

Subscribe to this mod's changes

hermes-deploy-guard is an agent published in the GitHub repository davidgut1982/hermes-toolkit (2 stars, last pushed 5mo ago), licensed MIT. It adds 128 tokens to every session and 1,007 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Cloud DevOps and cloud

hermes-deploy-guard next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
hermes-deploy-guarddavidgut1982/hermes-toolkit	Agent	2	5mo ago	MIT	A	128	Claude Code
it-engineerserejaris/personal-corp-os	Agent	243	4d ago	MIT	A	66	Claude Code
cloud-agentTyrusRC/praetor	Agent	8	2d ago	Apache-2.0	A	53	Claude Code
database-migrationivegamsft/basecoat	Agent	4	8d ago	MIT	A	37	Claude Code
azure-architectarmanzeroeight/fastagent-plugins	Agent	29	3mo ago	MIT	A	35	Claude Code
deployment-verifierasysta-act/agent-flow	Agent	12	4mo ago	MIT	A	24	Claude Code
aws-principal-architectjiamaozheng/awesome-claude-code	Agent	1	today	none	A	25	Claude Code