discord-bridge — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited discord-bridge (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
The UNITARES Discord bridge is a standalone Python bot (in the unitares-discord-bridge repo) that polls both the governance MCP server and the anima MCP server, then forwards events and state to a Discord server. It turns governance into something visible — agent presence, EISV changes, dialectic sessions, knowledge graph updates, and Lumen's physical state all appear as Discord messages and embeds.
The bridge operates in 8 layers, each handling a different aspect:
The bridge can take autonomous governance actions, but only in response to governance events:
The bridge never modifies governance state unprompted. Autonomous actions only fire when governance events trigger them (pause, reject, critical drift, high risk score).
The Discord server is organized into 5 categories with 13+ channels and 2 forum channels:
| Category | Channels | Purpose |
|---|---|---|
| GOVERNANCE | events, verdicts, alerts, system-hud | Core governance activity |
| AGENTS | presence, check-ins, agent-detail | Agent lifecycle and status |
| LUMEN | state, sensors, drawings, neural | Lumen's physical and computational state |
| KNOWLEDGE | discoveries, graph-updates, search | Knowledge graph activity |
| CONTROL | commands, config, audit-log | Bot configuration and audit trail |
Forum channels are used for dialectic sessions (one thread per session) and knowledge discussions.
Required environment variables:
| Variable | Description |
|---|---|
DISCORD_BOT_TOKEN | Discord bot token with appropriate permissions |
DISCORD_GUILD_ID | Target Discord server ID |
GOVERNANCE_MCP_URL | Governance MCP endpoint (default: http://localhost:8767/mcp/) |
ANIMA_MCP_URL | Anima MCP endpoint (default: http://<pi-tailscale-ip>:8766/mcp/ — get IP from tailscale status) |
# Install
pip install -e .
# Run
python -m bridge.botThe bot will create missing channels on first startup and begin polling both MCP servers.
Key design decisions:
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.