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 skills add automateyournetwork/netclaw --skill hermes-hud-diagnosticsgit clone --depth 1 https://github.com/automateyournetwork/netclawWrote 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/skills/automateyournetwork/netclaw/hermes-hud-diagnostics)<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/hermes-hud-diagnostics"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/hermes-hud-diagnostics/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.
<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/hermes-hud-diagnostics"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/hermes-hud-diagnostics.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00025 | $0.00414 |
| Opus 5.5 | $0.00010 | $0.00166 |
| Sonnet 5.5 | $0.00005 | $0.00083 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
hermes-hud-diagnostics 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 9d 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.
What it actually says
Hermes HUD diagnostics
Use for a Hermes installation whose shared HUD is unavailable, incorrectly selected, or showing an uncertain request. Read docs/HERMES-HUD.md and mcp-servers/hermes-hud-mcp/README.md in the NetClaw checkout.
- Run
./scripts/netclaw hud statusfrom the checkout. Observe selection, configuration presence, authenticated companion readiness, qualified tools and separately reported execution verification. Do not print provider credentials or private transcript contents. - If selection is wrong, explain the intended
hud select hermes /absolute/homechange before making an owner-requested switch. Do not infer a home from OpenClaw data. - Missing component needs
./scripts/install.sh --runtime hermes --add hermes-hud; start only when requested. Never restart the owner's Hermes gateway as a diagnostic shortcut. - A source/policy mismatch requires requalification or restoration of the pinned source. Do not disable protection, register unreviewed tools or silently switch to OpenClaw.
- Unknown work is reconciled through its owned HUD status/history. Never resubmit it, infer cancellation from stop acknowledgment, or claim a device operation from assistant prose.
- Live provider/tool tests require the explicit acceptance workflow; a read-only status request does not authorize inference, tool execution or device access.
The bridge's eight tools are HUD-private. Do not add them to Hermes or OpenClaw MCP registries, call conversation submission from inside an agent, or broaden once/deny approvals. Initial qualification supports only the reviewed IPv4 subnet tool and static installed skill context. Writes, attachments, model/effort overrides, hosted Avatar and federation are unavailable; federation belongs to spec 149. Local Avatar shares Standard Chat without creating a run merely by switching views.
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.
- 9d ago First seen · 20 lines · 25 tokens per session scan A a6d3004b4be9
hermes-hud-diagnostics is a skill published in the GitHub repository automateyournetwork/netclaw (684 stars, last pushed 2d ago), licensed Apache-2.0. It adds 25 tokens to every session and 414 once invoked, about $0.0001 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-10-11.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…