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/jochenyang/agent-comm-hub/agentsnpx skills add JochenYang/agent-comm-hub --skill agentsgit clone --depth 1 https://github.com/JochenYang/agent-comm-hubWrote 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/jochenyang/agent-comm-hub/agents)<a href="https://agentmods.dev/skills/jochenyang/agent-comm-hub/agents"><img src="https://agentmods.dev/badge/skills/jochenyang/agent-comm-hub/agents.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 | $0.00005 | $0.01088 |
| Opus 5 | $0.00003 | $0.00544 |
| Sonnet 5 | $0.00001 | $0.00218 |
| Haiku 4.5 | $0.00001 | $0.00109 |
Grade A, and why
agent-comm-hub 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agent-comm-hub usage
A local hub (agent-comm-hub on 127.0.0.1:18764) connects this agent with
every other MCP-capable agent on this machine (MiniMax Code, opencode, Kimi
Code, Claude Code, DeepSeek Harness, …).
You are already registered: connecting to the hub auto-registers you at
the MCP handshake using your client name — no manual step needed. Same-name
connections share one peer id, so your identity is stable across sessions.
Optional: call bridge_register(peerId) to claim a readable id
(tool:project, e.g. claude-code:myproject; errors when taken).
Tools
bridge_chat(to, message)— send a chat message to a peer;to: "all"broadcasts.bridge_task(to, prompt, context?, deliverable?)— delegate a structured task.bridge_ack(ref, status, note?)— acknowledge a task (accepted/rejected/done/failed), auto-routed back to the original sender.bridge_wait(from?, timeoutMs?)— long-poll for the next message (default 30 s; loop it to hold a real-time conversation).bridge_poll(from?)— non-blocking drain of every queued message.bridge_status()/bridge_peers()— hub health and who is online.bridge_history(peer?, limit?)— recent messages (newest first).peerdefaults to you; pass another peer's id to read their conversation, or"all"for the unfiltered tail across every peer.
When to use
- The user mentions "another agent / the hub / over there" pointing at a different agent — use the bridge tools.
- Before messaging a specific agent, call
bridge_peers()first and use its exact peerId. If the target is not listed, it is not connected yet — do NOT guess a peerId or send blindly; tell the user the other agent needs to be running (it registers automatically on connect). - Receiving: try
bridge_poll()first; if empty, loopbridge_wait()until a message arrives or you give up. - On receiving a
task(content is{prompt, context?, deliverable?}): acknowledge withbridge_ack(ref, "accepted")when you take it on, thenbridge_ack(ref, "done"[, note])when finished; use"rejected"to decline and"failed"when it could not be completed (always with a note). - Unsure whether the peer is online: check
bridge_peers()first.
What ships with it
13 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.
- claude-code/.mcp.json 115 B
- codex/config.toml 84 B
- dsh/cordis.patch.yml 196 B
- gemini-cli/settings.json 115 B
- install-all.ps1 8.7 KB runs code
- kimi-code/mcp-entry.json 184 B
- minimax-code/install-mcode.ps1 4.5 KB runs code
- minimax-code/mcp-entry.json 407 B
- minimax-code/SKILL.md 2.9 KB
- opencode/opencode.json 133 B
- README.md 2.9 KB
- registry.json 4.9 KB
- zcode/config.json 166 B
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 · 90 lines · 0 tokens per session scan A 9cb6842fef21
agent-comm-hub is a skill published in the GitHub repository JochenYang/agent-comm-hub (4 stars, last pushed 6d ago), licensed MIT. It adds 5 tokens to every session and 1,088 once invoked, about $0.0000 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…