Pilot Event Bus
Security checks across static analysis, malware telemetry, and agentic risk
Overview
This is a coherent Pilot Protocol pub/sub helper, but it intentionally lets agents publish events, subscribe to topics, and establish trust with other agents, so host, topic, and trust choices matter.
This skill appears safe for its stated purpose if you already trust Pilot Protocol, pilotctl, and the participating agents. Before using it, verify hostnames, approve any new trust handshakes, avoid broad wildcard topics for important actions, and keep sensitive data out of event payloads unless all subscribers are trusted.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
An agent using this skill can issue event-bus commands that other trusted agents may act on.
The skill grants Bash use to run pilotctl pub/sub commands. This is central to the stated purpose, but incorrect host, topic, or payload choices could affect coordinated workflows.
allowed-tools: - Bash ... pilotctl --json publish <target-hostname> <topic> --data <payload>
Keep Bash usage scoped to the documented pilotctl commands and review target hostnames, topics, and payloads before high-impact publishes.
Trusting the wrong hostname could allow an unintended agent to receive or send coordination events.
The skill includes trust-listing and trust-establishment operations. This is purpose-aligned for multi-agent coordination, but it changes which agents can participate.
All participating agents must have mutual trust established ... pilotctl --json handshake <hostname> "reason for trust request"
Require explicit user approval before new handshakes, verify host identities, and periodically review the trusted-agent list.
The safety of the workflow depends on the installed pilotctl binary and daemon being trustworthy.
The core behavior depends on external Pilot Protocol components that are not included or scanned in this instruction-only artifact.
Requires pilot-protocol skill and pilotctl binary on PATH. The daemon must be running (pilotctl daemon start).
Install pilotctl and the Pilot Protocol skill from trusted sources and review those components separately.
Event payloads may be visible to or acted on by trusted subscribed agents.
The skill is designed to move event payloads between agents over a shared pub/sub channel. That is expected for the purpose, but it crosses agent and network boundaries.
Multi-agent event aggregation using Pilot Protocol's built-in pub/sub on port 1002.
Only use this with mutually trusted agents, avoid unnecessary sensitive data in payloads, and scope topics narrowly.
A mistaken or overly broad event could trigger multiple agents or workflows.
The documented fan-out and wildcard topic behavior can propagate one event to many agents. This is the intended event-bus function, but mistakes can cascade.
broadcast events to all subscribed agents ... coordinate state changes across a fleet of agents ... Wildcards: tasks.*, alerts.error.*, *
Prefer specific topics over broad wildcards, use timeouts, and add human confirmation for events that could cause high-impact state changes.