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 howdeploy/deploychan_mcp --skill hermes-maintenancegit clone --depth 1 https://github.com/howdeploy/deploychan_mcpWrote 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/howdeploy/deploychan_mcp/hermes-maintenance)<a href="https://agentmods.dev/skills/howdeploy/deploychan_mcp/hermes-maintenance"><img src="https://agentmods.dev/badge/skills/howdeploy/deploychan_mcp/hermes-maintenance/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/howdeploy/deploychan_mcp/hermes-maintenance"><img src="https://agentmods.dev/badge/skills/howdeploy/deploychan_mcp/hermes-maintenance.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.00063 | $0.00850 |
| Opus 5.5 | $0.00025 | $0.00340 |
| Sonnet 5.5 | $0.00013 | $0.00170 |
| Haiku 4.5 | $0.00006 | $0.00085 |
Grade A, and why
Diagnose and repair Hermes Agent 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 3d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hermes maintenance
Work on the requested installation and symptom. An audit does not authorize changing settings; a repair does not authorize deleting procedures, clearing conversations, rewriting identity or disabling unrelated automation. Preserve existing authorization and verification limits. This skill adds no requirement for extra agents or model calls.
Select a branch
Retrieve only the relevant guide through this MCP's get_item(item_id):
| Symptom | Item to retrieve |
|---|---|
| Wrong profile, stale code/prompt, update conflict or suspected bad commit | hermes-runtime-and-upgrades |
| Uncertain software availability, launch history, silent failures or unsupported agent claims | hermes-runtime-and-upgrades |
| Skills multiply, lose categories, disappear, or contradict memory/project instructions | hermes-skills-and-context |
| Checkpoint failures, missing paths, unexpected Git work or long task latency | hermes-checkpoints-and-latency |
For an ordered maintenance engagement, retrieve route hermes-repair-and-optimization
with get_item, or use onboard with a Hermes repair goal and follow its returned IDs.
Routes are optional navigation; a known fault can go directly to its branch.
Shared procedure
- Identify the live gateway, its checkout, interpreter, effective Hermes home, profile, working directory and terminal backend. Compare these with the files being inspected.
- Preserve the exact failing operation and error. Distinguish a source defect, configuration choice, stale process, stale session, missing prerequisite and unproven hypothesis. For a historical audit, correlate saved calls/results and logs within a stated time range, and compare them with the agent's reports. Separate attempts, confirmed success/failure and unknown outcomes. A commit title or an agent's explanation does not establish a cause.
- Read the installed implementation and relevant release documentation. Find every caller or writer of the affected resource before changing a shared policy.
- Make the smallest authorized correction. Preserve a rollback artifact and unrelated dirty changes. Repair writer policy before reorganizing a library that can regrow.
- Apply the change at the required layer: configuration reload, idle graceful restart, or a new conversation. Do not assume all three are interchangeable.
- Verify the requested behavior with permitted evidence. Separate static inspection, helper-level checks, live process state and a real end-to-end task. Never claim an unperformed test; report pending activation or verification explicitly.
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.
- 3d ago First seen · 77 lines · 63 tokens per session scan A 93ec519295c9
Diagnose and repair Hermes Agent is a skill published in the GitHub repository howdeploy/deploychan_mcp (18 stars, last pushed 3d ago), licensed MIT. It adds 63 tokens to every session and 850 once invoked, about $0.0003 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-18.
Other skills, from other repositories
skill-auditor
Use when auditing Hermes skills for broken references.
mnemosyne-maintenance
Use when: upgrading Mnemosyne, diagnosing slow/hung consolidation (mnemosynesleep), fixing missing embeddings, or troubleshooting import/version mismatches.
mnemosyne-maintenance
Use when: upgrading Mnemosyne, diagnosing slow/hung consolidation (mnemosynesleep), fixing missing embeddings, or troubleshooting import/version mismatches.
gcp-cloud-logging
Google Cloud Logging — log search, VPC flow logs, firewall logs, audit logs, log buckets and views. Use when searching GCP logs, investigating denied VPC flow traffic, checking who deleted a VM, analyzing firewall rule hits, or troubleshooting a GCP application error.
hermes-self-evaluation
Use this skill when the user asks to audit, review, or optimize Hermes's own performance — analyzing session data, skills, configuration, costs, and usage patterns to identify improvements, automation opportunities, and system optimizations.
janitor-fix
Automatically fix skill problems (safe preview first). Also use with --prune to find and remove broken symlinks, empty directories, and orphaned skills. Trigger with '/janitor-fix'.