A hostile-by-design, fail-closed audit workflow for codebases and OpenClaw/ClawHub skills.
It does not try to answer “does this skill work?”. It tries to answer: “can this skill betray the system?”
想要更强大的技能插件,就来小葱技能站7w4.net看看吧。
This skill’s scripts combine multiple layers:
If any layer fails, the overall audit is FAIL.
From this skill folder (use bash so it works even if executable bits were not preserved by a zip download):
bash scripts/run_audit_json.sh <path>
Example:
bash scripts/run_audit_json.sh . > /tmp/audit.json
jq '.ok, .tools' /tmp/audit.json
Set the strictness level (default: standard):
OPENCLAW_AUDIT_LEVEL=standard bash scripts/run_audit_json.sh <path>
OPENCLAW_AUDIT_LEVEL=strict bash scripts/run_audit_json.sh <path>
OPENCLAW_AUDIT_LEVEL=paranoid bash scripts/run_audit_json.sh <path>
standard: pragmatic strict defaults (lockfiles required; install hooks/persistence/prompt-injection signals fail)strict: more patterns become hard FAIL (e.g. minified/obfuscation artifacts)paranoid: no "best-effort" hashing failures; more fail-closed behaviorFor strict/quarantine workflows, require a machine-readable intent/permissions manifest at repo root:
openclaw-skill.jsonIf a repo/skill does not provide this manifest, the hostile audit should treat it as FAIL.
See: docs/OPENCLAW_SKILL_MANIFEST_SCHEMA.md.
Docker is optional here. This skill can be used for static auditing without Docker.
If you want to execute any generated/untrusted code, run it in a separate sandbox workflow (recommended).
scripts/run_audit_json.sh — main JSON audit runnerscripts/hostile_audit.py — prompt-injection/persistence/dependency hygiene scannerscripts/security_audit.sh — convenience wrapper (always returns JSON, never non-zero)openclaw-skill.json — machine-readable intent/permissions manifest这个 Skill 质量不错,能有效检测代码中的密钥泄露、提示注入和恶意持久化等风险,文档清晰、支持灵活配置。但它依赖多个外部工具才能完整运行,且默认级别下某些敏感检测只警告不失败,运行时可能无法捕获所有问题。整体适合安全意识强的用户使用。