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.
npx agentmods add agents/davidgut1982/hermes-toolkit/hermes-deploy-guardgit clone --depth 1 https://github.com/davidgut1982/hermes-toolkitWrote 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.
[](https://agentmods.dev/agents/davidgut1982/hermes-toolkit/hermes-deploy-guard)<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="Measured on agentmods" height="20"></a>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 | $0.00128 | $0.01007 |
| Opus 5 | $0.00064 | $0.00504 |
| Sonnet 5 | $0.00026 | $0.00201 |
| Haiku 4.5 | $0.00013 | $0.00101 |
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 4d 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.
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-agentMUST stay on branchintegrated(it carries profile-aware delegation). Two prior outages came from an agentgit checkout-ing a feature branch on the live tree. - You never
git checkouta different branch on the live tree. Dev work goes in agit worktreeor underhermes -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 beintegrated. 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.)
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.
- 4d ago First seen · 73 lines · 128 tokens per session scan A 302fa6dd29fd
hermes-deploy-guard is an agent published in the GitHub repository davidgut1982/hermes-toolkit (2 stars, last pushed 3mo ago), licensed MIT. It adds 128 tokens to every session and 1,007 once invoked, about $0.0006 per session on Opus 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.
Other agents, from other repositories
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
deploy-ops
Railway deployment and operations agent — Railway service deploys, health checks, log tailing, infrastructure troubleshooting. Use for deployment and ops tasks.
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.