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/aannoo/hcom/hcom-agent-messagingnpx skills add aannoo/hcom --skill hcom-agent-messaginggit clone --depth 1 https://github.com/aannoo/hcomWrote 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/aannoo/hcom/hcom-agent-messaging)<a href="https://agentmods.dev/skills/aannoo/hcom/hcom-agent-messaging"><img src="https://agentmods.dev/badge/skills/aannoo/hcom/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 | $0.00042 | $0.01662 |
| Opus 5 | $0.00021 | $0.00831 |
| Sonnet 5 | $0.00008 | $0.00332 |
| Haiku 4.5 | $0.00004 | $0.00166 |
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 4d 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 — 191 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.
curl -fsSL https://github.com/aannoo/hcom/releases/latest/download/hcom-installer.sh | sh
hcom claude # or: hcom gemini, hcom codex, hcom opencode, hcom kilo, hcom pi, hcom omp, hcom agy, hcom cursor-agent, hcom kimi, hcom copilot
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 |
| kilo code | automatic | hcom kilo |
| antigravity | automatic | hcom agy |
| cursor | automatic | hcom cursor-agent |
| 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 4.8 KB
- references/gotchas.md 6.3 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.
- 4d ago First seen · 191 lines · 42 tokens per session scan C 7714c97abebc
hcom-agent-messaging is a skill published in the GitHub repository aannoo/hcom (475 stars, last pushed 25d ago), licensed MIT. It adds 42 tokens to every session and 1,662 once invoked, about $0.0002 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-30.
Other skills, from other repositories
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…
golang-dependency-injection
Comprehensive guide for dependency injection (DI) in Golang. Covers why DI matters (testability, loose coupling, separation of concerns, lifecycle management), manual constructor injection, and DI library comparison (google/wire, uber-go/dig, uber-go/fx, samber/do). Use this skill when designing service architecture…
golang-troubleshooting
Troubleshoot Golang programs systematically - find and fix the root cause. Use when encountering bugs, crashes, deadlocks, races, or unexpected behavior in Go code. Covers debugging methodology, common Go pitfalls, test-driven debugging, pprof setup and capture, Delve, race detection, GODEBUG tracing, and production…
golang-cli
Golang CLI application development. Use when building, modifying, or reviewing a Go CLI tool — especially for command structure, flag handling, configuration layering, version embedding, exit codes, I/O patterns, signal handling, shell completion, argument validation, and CLI unit testing. Also triggers when code uses…
golang-code-style
Golang code style conventions — line length and breaking, variable declarations, control flow clarity, when comments help vs hurt. Use when writing or reviewing Go code, asking about style or clarity, or establishing project coding standards. Not for naming conventions (→ See samber/cc-skills-golang@golang-naming…
golang-grpc
Provides gRPC usage guidelines, protobuf organization, and production-ready patterns for Golang microservices. Use when implementing, reviewing, or debugging gRPC servers/clients, writing proto files, setting up interceptors, handling gRPC errors with status codes, configuring TLS/mTLS, testing with bufconn, or…