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 AtlasOmnia/hermes-custom-pack --skill messaging-gateway-troubleshootinggit clone --depth 1 https://github.com/AtlasOmnia/hermes-custom-packWrote 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/atlasomnia/hermes-custom-pack/messaging-gateway-troubleshooting)<a href="https://agentmods.dev/skills/atlasomnia/hermes-custom-pack/messaging-gateway-troubleshooting"><img src="https://agentmods.dev/badge/skills/atlasomnia/hermes-custom-pack/messaging-gateway-troubleshooting/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/atlasomnia/hermes-custom-pack/messaging-gateway-troubleshooting"><img src="https://agentmods.dev/badge/skills/atlasomnia/hermes-custom-pack/messaging-gateway-troubleshooting.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.00037 | $0.01173 |
| Opus 5.5 | $0.00015 | $0.00469 |
| Sonnet 5.5 | $0.00007 | $0.00235 |
| Haiku 4.5 | $0.00004 | $0.00117 |
Grade A, and why
messaging-gateway-troubleshooting scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- On macOS, do not assume `localhost` reaches an IPv4-only Hermes webhook. BlueBubbles/Electron/Node may resolve `localhost` to IPv6 `::1`, causing `connect ECONNREFUSED ::1:<port>` while `curl http://127.0.0.1:<port>/he This is a copy
100% identical to messaging-gateway-troubleshooting — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Messaging Gateway Troubleshooting
Use this when Hermes messaging platforms are installed/configured but messages do not arrive, are ignored, do not reply, or appear to risk reply loops.
Operating principles
- Verify the live path end to end before assuming config is wrong:
- Gateway service is running.
- Platform server/client is running.
- Local webhook/listener is bound.
- Health endpoint responds if available.
- Platform has the webhook registered.
- Gateway logs show the adapter connected.
- Separate transport, authorization, and adapter filtering:
- Transport failure: no webhook hit / listener closed.
- Authorization failure: sender not allowed or pairing pending.
- Adapter filtering: message acknowledged but intentionally skipped, e.g. group mention gating, tapback filtering, or self-message loop guard.
- For user-visible claims, verify with real command output:
hermes status, listener checks, webhook health, and gateway logs. - When changing Hermes gateway config or adapter code, restart the gateway and verify the adapter reconnects.
- For gateway slash-command failures, inspect session-origin scope separately from transport health:
- Compare
source,user_id,chat_id,thread_id, andorigin_jsonin the live session database. - Trace both the listing path and the action path; a session browser is still broken if it lists a target that
/resumerejects. - In forum/threaded platforms, distinguish same-parent-chat ownership from exact-thread isolation rather than weakening origin checks globally.
Telegram forum session browsing
- A fresh Telegram forum topic can have no prior exact-thread sessions even when the same owner has many titled sessions in sibling topics of the same parent chat.
- Do not diagnose this from session history alone. Correlate gateway send logs, live DB origin columns, and the gateway routing origin.
- Cross-topic browsing must be Telegram-specific, same-parent-chat, and same-owner;
thread_sessions_per_user=falsepermits sharing within one thread, not across sibling threads. - Keep
/sessionsvisibility and/resumeauthorization aligned, including persisted-only rows. - See
references/telegram-forum-session-scope.mdfor the reproduction, authorization contract, TDD matrix, and safe activation procedure.
What ships with it
3 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.
- 1mo ago First seen · 81 lines · 37 tokens per session scan A 8bcb362bf3e1
messaging-gateway-troubleshooting is a skill published in the GitHub repository AtlasOmnia/hermes-custom-pack (72 stars, last pushed 13d ago), licensed MIT. It adds 37 tokens to every session and 1,173 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to messaging-gateway-troubleshooting, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
messaging-gateway-troubleshooting
Use this when Hermes messaging platforms are installed/configured but messages do not arrive, are ignored, do not reply, or appear to risk reply loops.
notebooklm
Install, authenticate, troubleshoot, and operate Gemini Notebook through the notebooklm-py CLI or typed async Python API. Use for notebook and source management, grounded chat and research, and artifact generation or download when the user mentions Gemini Notebook, notebooklm-py, the notebooklm CLI, or its Python API.…
api-errors
McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.
hunt-wordpress
Use when an authorized target exposes WordPress core, plugin, theme, REST, or XML-RPC behavior.
verify-before-done
Before claiming work is fixed, done, passing or deployed.
hermes-plugin-development
Use when: creating, debugging, or integrating Hermes Agent plugins, including Python backend plugins (tools, hooks, routers, middleware) and JavaScript Hermes Desktop runtime plugins.