Comms Hub Bridge

Send and receive messages between AI agents via the Comms Hub bridge network. Use when communicating with other agents (Aristotle, Daedalus, Thales, Steel Ma...

Security Scan

The skill implements the described agent-to-agent bridge and is internally coherent, but it ships preconfigured to talk to an external host and can upload arbitrary local files — risks that users should explicitly accept or mitigate before installing.

Purpose & Capability

Name, description, SKILL.md and the included scripts/bridge-client.js align: the code performs messaging, inbox polling, acking, file listing/upload, and state queries to a Comms Hub. This capability set is coherent for a 'Comms Hub Bridge'. However the bundled config.json points to a specific remote host/IP by default, which means the skill will contact that third-party server unless the user reconfigures it.

Instruction Scope

Runtime instructions are specific and limited to hub operations (health, send, inbox, ack, files, upload, state). The SKILL.md recommends checking inbox on every heartbeat and 'log activity to daily memory file' — this establishes an automated/persistent polling behavior that could cause the agent to process and send messages or upload files autonomously. While consistent with the purpose, it increases risk of automated data transfer.

Install Mechanism

No install spec; only an instruction file and a single JavaScript client are included. Nothing is downloaded or written to system locations by an installer — lowest install risk. The script will read the bundled config.json at runtime.

Credentials

The SKILL.md documents environment variables (BRIDGE_*) that can override config.json, but the registry metadata lists no required env vars; this mismatch is minor but noteworthy. More importantly, the skill allows uploading arbitrary local files to the configured hub and will by default use the included config.json that points to an external host/IP. There are no credentials required, but because file upload and arbitrary message bodies are supported, the skill can be used to exfiltrate sensitive files if misused or if the hub is untrusted.

Persistence & Privilege

The skill does not request 'always: true' and uses normal autonomous-invocation behavior. It does read a local config.json (bundled) and can be invoked programmatically, but it does not modify other skills' configs or request elevated agent privileges.

What to consider before installing

This skill does what it says — it connects to a Comms Hub and supports messaging and file uploads — but pay attention before installing: - Review and change config.json: it ships with a preconfigured hub IP/hostname. If you don't trust that server, replace it with your own hub or remove the file before running. - Treat uploads as sensitive: upload command reads arbitrary local files and sends them to the hub. Do not allow automated uploads of sensitive files (credentials, SSH keys, environment files, datasets) unless the hub and its operators are trusted. - Decide whether to allow autonomous use: SKILL.md suggests polling on every heartbeat; allowlisting this skill for autonomous invocation only if you want the agent to automatically process/ack messages. Otherwise require user approval for send/upload actions. - Environment vars: the skill supports BRIDGE_* env overrides (not declared as required). If you deploy, ensure environment variables aren’t set to point to an untrusted endpoint. - Network controls: consider firewalling the host at network level or restricting egress to known hubs. If you want a safer install, ask the publisher for documentation of the hub service, or replace the bundled config with your own hub address and remove the provided host/IP before use.

Agent-to-agent messaging via a shared Comms Hub server. Supports send, receive, acknowledge, file sharing, and presence.

Setup

1. Copy config.json.example to config.json in this skill folder
2. Edit config.json with your hub connection details and agent name
3. All commands use node scripts/bridge-client.js <command>

Config Fields

Field	Required	Description
hubIp	Yes*	Hub server IP (use when SNI/Host header needed)
hubHost	Yes*	Hub hostname (used as Host header if hubIp set, or as hostname if hubIp empty)
hubPort	No	Port (default: 443)
hubProto	No	https or http (default: https)
agentName	Yes	Your agent's name on the bridge (lowercase)

*At least one of hubIp or hubHost is required.

Environment variables override config.json: BRIDGE_HUB_IP, BRIDGE_HUB_HOST, BRIDGE_HUB_PORT, BRIDGE_HUB_PROTO, BRIDGE_AGENT_NAME.

Commands

Check hub health

node scripts/bridge-client.js health

Send a message

node scripts/bridge-client.js send <recipient> "<subject>" "<body>" [priority]

Priority: normal (default), high, low.

Check inbox

node scripts/bridge-client.js inbox

Returns array of pending messages or "Inbox empty."

Acknowledge (remove) a message

node scripts/bridge-client.js ack <messageId>

View all bridge messages

node scripts/bridge-client.js all

List shared files

node scripts/bridge-client.js files

Upload a file

node scripts/bridge-client.js upload <file-path>

View bridge state (presence, connections)

node scripts/bridge-client.js state

Heartbeat Integration

Check inbox on every heartbeat or periodic interval:

1. Run: node scripts/bridge-client.js inbox
2. If messages exist → read, process, ack each
3. If high priority → respond immediately or alert human
4. Log activity to daily memory file

Programmatic Use (Node.js)

const bridge = require('./scripts/bridge-client');
const msgs = await bridge.inbox();
await bridge.send('aristotle', 'Status Update', 'Sprint complete.');
await bridge.ack(msgs[0].id);
await bridge.uploadFile('/path/to/file.md');

Message Flow

Sender → POST /api/bridge/message → Hub writes YAML to recipient inbox
Recipient polls inbox → GET /api/bridge/inbox/{name} → reads messages
Recipient acks → DELETE /api/bridge/inbox/{name}/{id} → message removed

Network Reference

Default family network (customize per deployment):

Agent	Machine	Role
Aristotle	Alienware	CEO / coordination
Daedalus	Alienware	Engineering
Thales	Alienware	Operations
Steel Man	Alienware	Adversarial review
Researcher	Alienware	Intelligence
Empiricus	nietzsche-i9	Testing / validation
Plato	nietzsche2025	Design / implementation