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 skills/gaelic-ghost/socket/operate-hermes-agent-gatewaynpx skills add gaelic-ghost/socket --skill operate-hermes-agent-gatewaygit clone --depth 1 https://github.com/gaelic-ghost/socketWrote 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/gaelic-ghost/socket/operate-hermes-agent-gateway)<a href="https://agentmods.dev/skills/gaelic-ghost/socket/operate-hermes-agent-gateway"><img src="https://agentmods.dev/badge/skills/gaelic-ghost/socket/operate-hermes-agent-gateway.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.1 | $0.00043 | $0.00771 |
| Opus 5 | $0.00022 | $0.00385 |
| Sonnet 5 | $0.00009 | $0.00154 |
| Haiku 4.5 | $0.00004 | $0.00077 |
Grade A, and why
operate-hermes-agent-gateway 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 5d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operate Hermes Agent Gateway
Treat the messaging gateway as a long-running service with external identities, inbound events, persistent sessions, and delivery obligations.
Define the Deployment
- Name the platform or API surface.
- Name the Hermes profile that owns its config, credentials, memory, sessions, skills, and gateway state.
- Choose the host and terminal backend.
- Define authorized users, chats, workspaces, or webhook senders before enabling actions.
- Define delivery behavior for replies, media, scheduled work, and failures.
- Define process supervision and logs through Hermes-supported or OS-supported service paths; do not invent a second gateway manager.
Keep Gateway Surfaces Distinct
- Messaging gateway:
hermes gatewayand its platform adapters. - API server: OpenAI-compatible HTTP endpoint hosted by the gateway.
- Inbound webhooks: authenticated event routes that trigger agent work.
- Outbound webhooks: signed delivery of Hermes events to a configured receiver; they are not inbound prompt endpoints.
- A2A platform: peer-agent discovery and tasks; hand its protocol lifecycle to
operate-a2a-agent-integration. - TUI gateway: JSON-RPC host protocol, not the messaging service.
- Nous Tool Gateway: hosted tool backends, not message transport.
Configure Safely
- Use a dedicated profile when a bot identity or authorization boundary differs.
- Keep platform tokens and API server keys in private configuration.
- Use separate secrets for inbound sender authentication and outbound webhook signatures. Verify signatures over the exact documented bytes before parsing or acting on a delivery.
- Bind local dashboards and APIs to localhost by default.
- Require explicit authentication and network controls before exposing an API or dashboard beyond localhost.
- Use platform allowlists and Hermes user authorization; do not rely on obscurity or a private-looking channel name.
- Prefer containerized or managed terminal backends for unattended public gateways.
- Preserve per-platform toolset differences rather than enabling every local tool everywhere.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 80 lines · 43 tokens per session scan A e7ee7d6b1ee6
operate-hermes-agent-gateway is a skill published in the GitHub repository gaelic-ghost/socket (7 stars, last pushed 10d ago), licensed Apache-2.0. It adds 43 tokens to every session and 771 once invoked, about $0.0002 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
pipeline
Use when the user wants a feature idea taken end-to-end in one autonomous run — phrases like "run the whole pipeline", "take this feature from idea to finished branch", "brainstorm then build it autonomously", "do everything from idea to merged", "implement all phases without stopping". Triggers when they want…
craft
Use when a product idea is still vague and needs to become a clear definition of what to build — "let's craft an app like X", "help me define what I actually want", "clarify this idea before we plan it". Also use before planning or implementation when requirements, UX, domain behaviour, or technical preferences have…
bug-fix
Use when a bug, regression, or unexpected behaviour is reported and the user wants it fixed end to end — "why is X broken", "this stopped working after Y", "fix this crash". Also use when a symptom is known but its cause is not. Not for building new behaviour, and not for a change whose cause is already proven.
bug-investigate
Use when someone wants to know WHY something is broken and has not asked for it to be fixed — "why is this happening", "what's causing this error", "find out what's wrong", "diagnose this before we decide". Also use before committing to a fix, when the cause is unknown and the decision depends on it. Not for fixing …
setup
Use when superb's skills need their dependencies installed or checked — "set up superb", "install the dependencies", "why does pipeline say superpowers is missing", after a fresh plugin install, or on a new machine. Also use when a skill fails complaining that a superpowers sub-skill cannot be found.
chief-financial-officer
Owns the financial position: planning, budgeting, forecasting, unit economics, cash, and the numbers the business is run and reported on. Use this to build or challenge a budget, model a decision's financial consequence, assess unit economics or runway, evaluate an investment or spend request, set financial controls…