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 davidgut1982/hermes-toolkit --skill hermes-orchestration-routinggit 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/skills/davidgut1982/hermes-toolkit/hermes-orchestration-routing)<a href="https://agentmods.dev/skills/davidgut1982/hermes-toolkit/hermes-orchestration-routing"><img src="https://agentmods.dev/badge/skills/davidgut1982/hermes-toolkit/hermes-orchestration-routing/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/davidgut1982/hermes-toolkit/hermes-orchestration-routing"><img src="https://agentmods.dev/badge/skills/davidgut1982/hermes-toolkit/hermes-orchestration-routing.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.00172 | $0.01563 |
| Opus 5 | $0.00086 | $0.00781 |
| Sonnet 5 | $0.00034 | $0.00313 |
| Haiku 4.5 | $0.00017 | $0.00156 |
Grade A, and why
hermes-orchestration-routing 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 10d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hermes Orchestration Routing
The single biggest lever on latency and reliability for a Hermes orchestrator is matching the execution mechanism to the task. Get this wrong and a question that should be one tool call becomes a 6–17 model-call delegation that wanders.
The core rule
Deterministic single-command facts → ONE direct tool call. Reasoning / judgment / multi-step →
delegate_task. Never delegate a status check. Never KB-search before aservice_statuscall.
This was measured on the author's homelab build: simple ops ("is the gateway running?") routed
through delegate_task cost 6–17 model calls / 90–150s and sometimes timed
out; the correct path is a single cluster-ops.service_status call (~1–3
model turns). On the slow local model (apex-fast on a P40) the cost of getting
this wrong is severe because prefill dominates every extra turn.
DIRECT vs DELEGATE — the decision table
| The ask | Mechanism | Why |
|---|---|---|
| "is hermes-gateway running?" | cluster-ops service_status — direct |
deterministic, one command, one fact |
| "how much disk is free?" | cluster-ops disk_usage — direct |
same |
| "tail the gateway log" | cluster-ops journal_tail — direct |
same |
| "is the container up?" | cluster-ops docker_ps — direct |
same |
| "give me cluster health" | cluster-ops cluster_snapshot — direct |
one structured read |
| "debug why the gateway keeps crashing and propose a fix" | delegate_task |
investigation + judgment, not one command |
| "plan a migration of the lore DB" | delegate_task |
multi-step reasoning, a deliverable |
| "review this config and suggest improvements" | delegate_task |
judgment + recommendations |
If the answer is a single fact obtainable by a single deterministic command, call the tool. If it requires investigation, synthesis, a plan, or a judgment call, delegate.
Ops mechanism on this build: cluster-ops MCP (terminal is disabled)
terminal AND code_execution are in agent.disabled_toolsets — globally
disabled. Do not try to shell out for ops; it cannot fire. Use the
cluster-ops MCP instead:
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.
- 10d ago First seen · 129 lines · 172 tokens per session scan A f1d313c35e9f
hermes-orchestration-routing is a skill published in the GitHub repository davidgut1982/hermes-toolkit (2 stars, last pushed 3mo ago), licensed MIT. It adds 172 tokens to every session and 1,563 once invoked, about $0.0009 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…