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 scchearn/hcom-mcp --skill hcom-agent-messaginggit clone --depth 1 https://github.com/scchearn/hcom-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/scchearn/hcom-mcp/hcom-agent-messaging)<a href="https://agentmods.dev/skills/scchearn/hcom-mcp/hcom-agent-messaging"><img src="https://agentmods.dev/badge/skills/scchearn/hcom-mcp/hcom-agent-messaging.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.00060 | $0.01863 |
| Opus 5 | $0.00030 | $0.00932 |
| Sonnet 5 | $0.00012 | $0.00373 |
| Haiku 4.5 | $0.00006 | $0.00186 |
Grade C, and why
hcom-agent-messaging scanned grade C with 2 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 6d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://github.com/aannoo/hcom/releases/latest/download/hcom-installer.sh | sh Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://github.com/aannoo/hcom/releases/latest/download/hcom-installer.sh | sh How it starts
The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hcom — multi-agent communication for AI coding tools
AI agents running in separate terminals are isolated. hcom connects them via hooks and a shared database so they can message, watch, and spawn each other in real-time.
If the user wants a quick operating pattern from the current session, one headed hub with mostly headless workers, or practical thread and handoff defaults, use the separate using-hcom skill instead of this one.
curl -fsSL https://github.com/aannoo/hcom/releases/latest/download/hcom-installer.sh | sh
hcom claude # or: hcom gemini, hcom codex, hcom opencode
hcom # TUI dashboard
what humans can do
tell any agent:
send a message to claude
when codex goes idle send it the next task
watch gemini's file edits, review each and send feedback if any bugs
fork yourself to investigate the bug and report back
find which agent worked on terminal_id code, resume them and ask why it sucks
what agents can do
Message each other in real-time, bundle context for handoffs.
Observe each other: transcripts, file edits, terminal screens, command history.
Subscribe to each other: notify on status changes, file edits, specific events. React automatically.
Spawn, fork, resume, kill each other, in any terminal emulator.
run hcom --help for full command syntax and flags.
tool support
| tool | delivery | connect |
|---|---|---|
| claude code (incl. subagents) | automatic | hcom claude |
| gemini cli (>= 0.26.0) | automatic | hcom gemini |
| codex | automatic | hcom codex |
| opencode | automatic | hcom opencode |
| any other ai tool | manual via hcom listen |
hcom start (run inside tool) |
session binding (hcom transcript, hcom r/f by session id) happens on first message or first prompt for all hcom-launched tools.
setup
if the user invokes this skill without arguments:
- run
hcom status— if "command not found", install first:curl -fsSL https://github.com/aannoo/hcom/releases/latest/download/hcom-installer.sh | sh - run
hcom hooks addto install hooks for all detected tools - restart the AI tool for hooks to activate
What ships with it
10 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.
- references/cross-tool.md 2.8 KB
- references/gotchas.md 7.1 KB
- references/patterns.md 6.0 KB
- references/script-template.md 4.7 KB
- references/scripts/basic-messaging.sh 1.8 KB runs code
- references/scripts/cascade-pipeline.sh 2.1 KB runs code
- references/scripts/codex-worker.sh 1.8 KB runs code
- references/scripts/cross-tool-duo.sh 1.9 KB runs code
- references/scripts/ensemble-consensus.sh 1.8 KB runs code
- references/scripts/review-loop.sh 2.0 KB runs code
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.
- 6d ago First seen · 205 lines · 60 tokens per session scan C 1bda5133d2ed
hcom-agent-messaging is a skill published in the GitHub repository scchearn/hcom-mcp (1 stars, last pushed 13d ago), licensed MIT. It adds 60 tokens to every session and 1,863 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). 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…
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…
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…