Vinculum - Shared Consciousness
Analysis
Vinculum appears to be a coherent shared-memory relay skill, but users should only link trusted bots because it intentionally shares agent memory, decisions, and activity over a network and can run a local relay in the background.
Findings (6)
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.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
const child = spawn('node', [RELAY_SCRIPT, 'start', String(port)], {The skill launches a bundled Node relay script. The script path is fixed and this behavior is documented, but it is still local process execution.
detached: true, stdio: 'ignore', ... child.unref();
The relay is deliberately detached so it can keep running after the start command returns.
command: "cd $SKILL_DIR && npm install --production"
The skill installs Node dependencies to function. This is expected for the Gun.js relay, but users should recognize that npm packages are part of the trusted artifact set.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
Anyone with this code can read and write to shared context.
The invite/pairing code functions as an access secret for the shared collective and grants both read and write authority.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
Activity summaries | ✅ ... Learned knowledge | ✅ ... Decisions | ✅ ... Drone status | ✅
The skill intentionally shares persistent agent context and decisions across linked bots, which is its core purpose but also means shared content can influence future agent behavior.
if (!url || !url.startsWith('http')) { ... } ... peers.push(url);The peer command accepts any HTTP/HTTPS peer URL, so configured sync can extend beyond localhost or a LAN if the user adds such a peer.