Ai shield audit
14 AI executives powered by legendary minds (Musk/Buffett/Simons/Feynman) — deploy your virtual C-Suite in one git clone.
npx -y skills add aAAaqwq/AGI-Super-Team --skill ai-shield-auditAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Security audit engine for OpenClaw configurations. Detects vulnerabilities, misconfigurations, secret leaks, and over-privileged agents. Use when the user asks about security, hardening, config review, or audit of their OpenClaw setup.
SKILL.md
3.1 KB, as published. Nobody here has run it
OpenClaw Shield — Security Audit
Audit any OpenClaw config for security vulnerabilities, misconfigurations, and best-practice violations. Produces a structured JSON report with risk scores, findings, and remediation steps.
When to Use
- User asks to check/audit/review their OpenClaw security
- User wants to harden their config before deploying
- User is setting up a new OpenClaw instance
- User asks about secret leakage or API key exposure in their config
- Before publishing or sharing any config file
Quick Audit (live config)
node scripts/shield-audit.sh
Or directly:
node SKILL_DIR/bin/shield.js audit ~/.openclaw/openclaw.json --summary
What It Checks (11 categories)
- Gateway Auth — missing/weak auth, insecure UI settings
- Network Exposure — bind address, Tailscale funnel, wildcard proxies
- Channel Security — wildcard allowFrom, missing allowlists
- DM Policy — open DM policy without pairing
- Subagent Permissions — wildcard allowAgents, circular delegation chains, self-delegation
- Tool Permissions — over-privileged agents with tools.profile: "full"
- Secret Leakage — API keys, tokens, private keys in plaintext config
- Sandbox/Execution — missing workspace isolation, no execution policies
- Plugin Config — enabled plugins without channel config
- Heartbeat Exposure — sensitive data in heartbeat prompts
- Remote Config — unencrypted WebSocket, exposed remote URLs/tokens
Usage
Audit a config file
node SKILL_DIR/bin/shield.js audit <config.json>
node SKILL_DIR/bin/shield.js audit <config.json> --summary # human-readable
Audit from stdin
cat config.json | node SKILL_DIR/bin/shield.js audit --stdin
Sanitize a config (strip secrets)
node SKILL_DIR/bin/shield.js sanitize <config.json>
Programmatic use
const { auditConfig } = require('SKILL_DIR/src/audit');
const config = require('./openclaw.json');
const report = auditConfig(config);
console.log(report.risk_level); // "CRITICAL" | "HIGH" | "MEDIUM" | "LOW"
console.log(report.overall_score); // 0-100
console.log(report.vulnerabilities); // detailed findings
Output
Returns JSON with: risk_level, overall_score (0-100), vulnerabilities[], vulnerability_count, best_practices_compliance, action_recommended, safe_to_deploy, audit_timestamp.
Workflow for Agent
- Load the user's config:
cat ~/.openclaw/openclaw.json - Run:
node SKILL_DIR/bin/shield.js audit ~/.openclaw/openclaw.json --summary - Present findings to user with prioritized recommendations
- Offer to sanitize before sharing:
node SKILL_DIR/bin/shield.js sanitize <file>