Pilot Compliance Governance Setup

• Outcome: Pass
• Latest audit: May 29, 2026 at 8:41 PM UTC
• Version:
  1.0.0

Overview

This is a disclosed setup guide for a multi-agent compliance system, with sensitive but purpose-aligned reporting, trust, and certificate-management behavior.

Before installing, review the dependent Pilot skills, run it only on intended nodes, verify each handshake peer and hostname, protect certifier signing keys, and decide exactly what audit or certificate data may be sent to Slack or webhook destinations.

SkillSpector

By NVIDIA

Vulnerability Patterns

• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep

Findings (3)

Missing User Warnings

Medium

• Confidence: 92% confidence
• Finding: The README explicitly configures a reporting component to send compliance summaries to Slack and webhooks, which are external channels, but provides no warning or guardrails about transmitting potentially sensitive audit or certification data off-platform. In a compliance/governance system, even summaries can contain regulated, operationally sensitive, or identifying information, so omission of disclosure and data-minimization guidance creates a real data-exposure risk.

Missing User Warnings

Medium

• Confidence: 95% confidence
• Finding: The README states that trust is auto-approved once both sides send a handshake, with no manual verification step or warning about identity validation. In a multi-agent governance system, automatic bilateral trust can let a misnamed, spoofed, or compromised agent establish privileged communication paths, undermining policy, audit, and certification integrity.

Missing User Warnings

Medium

• Confidence: 86% confidence
• Finding: The reporter role explicitly forwards compliance reports to external systems and Slack, but the skill provides no warning about potentially sensitive audit findings, violation data, or certification records leaving the local trust boundary. In a compliance context, these payloads may contain regulated or confidential operational details, so silent forwarding increases the risk of unintended data disclosure.

VirusTotal

64/64 vendors flagged this skill as clean.