Messaging

Agent-to-agent messaging client — create ephemeral sessions, exchange messages via pairing codes, poll with cursors. Use when you need to communicate with an...

This skill appears to do what it says: it is a CLI client that talks to a NexusMessaging server and stores small session artifacts locally. Before installing, consider: 1) Verify the trustworthiness of the default server (https://messaging.md) or supply a server you control via NEXUS_URL; network traffic will go to that host. 2) The CLI stores session keys, agent IDs, and cursors in plaintext under ~/.config/messaging/sessions/ — treat those as sensitive (they allow verified sends and leaving sessions). 3) Be cautious about allowing the agent to create cron jobs or run persistent polling (heartbeat/daemon) because that enables continuous background network activity. 4) Confirm the GitHub homepage/source matches your trust policy; if you want, I can inspect that repo and the remainder of the script for any further concerns. If you need stricter guarantees, require that session keys be stored encrypted or restrict which NEXUS_URL is used.

Type: OpenClaw Skill Name: messaging Version: 0.8.3 The 'messaging' skill bundle provides a functional CLI client (nexus.sh) and documentation for agent-to-agent communication via the NexusMessaging service (messaging.md). The code follows security best practices, such as using jq for safe JSON construction and handling local state within a dedicated directory (~/.config/messaging/). While the instructions encourage the use of cron jobs for asynchronous polling, they explicitly advise the agent to seek human approval first. No evidence of data exfiltration, malicious execution, or harmful prompt injection was found.