How do I install the Security Audit skill?

Run npx skillmds@latest add aaaaqwq/security-audit in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Security Audit safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Security Audit?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Security Audit free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Security Audit?

aAAaqwq (@aaaaqwq) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Security Audit by aaaaqwq — Agent Skill

Name: Security Audit
Rating: 4.2 (5 reviews)
Author: aAAaqwq

File contents

security-audit

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?”

What it checks (high level)

This skill’s scripts combine multiple layers:

Secrets / credential leakage: trufflehog
Static analysis: semgrep (auto rules)
Hostile repo audit (custom): prompt-injection signals, persistence mechanisms, suspicious artifacts, dependency hygiene

If any layer fails, the overall audit is FAIL.

Run an audit (JSON)

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

Security levels (user configurable)

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 behavior

Manifest requirement (for zero-trust install workflows)

For strict/quarantine workflows, require a machine-readable intent/permissions manifest at repo root:

openclaw-skill.json

If a repo/skill does not provide this manifest, the hostile audit should treat it as FAIL.

See: docs/OPENCLAW_SKILL_MANIFEST_SCHEMA.md.

Optional: execution sandbox (Docker)

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).

Files

scripts/run_audit_json.sh — main JSON audit runner
scripts/hostile_audit.py — prompt-injection/persistence/dependency hygiene scanner
scripts/security_audit.sh — convenience wrapper (always returns JSON, never non-zero)
openclaw-skill.json — machine-readable intent/permissions manifest

---name: security-auditdescription: Fail-closed security auditing for OpenClaw/ClawHub skills & repos: trufflehog secrets scanning, semgrep SAST, prompt-injection/persistence signals, and supply-chain hygiene checks before enabling or installing.--- # security-audit 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?”** ## What it checks (high level) This skill’s scripts combine multiple layers: - **Secrets / credential leakage:** trufflehog - **Static analysis:** semgrep (auto rules) - **Hostile repo audit (custom):** prompt-injection signals, persistence mechanisms, suspicious artifacts, dependency hygiene If any layer fails, the overall audit is **FAIL**. ## Run an audit (JSON) From this skill folder (use `bash` so it works even if executable bits were not preserved by a zip download): ```bash bash scripts/run_audit_json.sh <path> ``` Example: ```bash bash scripts/run_audit_json.sh . > /tmp/audit.json jq '.ok, .tools' /tmp/audit.json ``` ### Security levels (user configurable) Set the strictness level (default: `standard`): ```bash 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 behavior ## Manifest requirement (for zero-trust install workflows) For strict/quarantine workflows, require a machine-readable intent/permissions manifest at repo root: - `openclaw-skill.json` If a repo/skill does not provide this manifest, the hostile audit should treat it as **FAIL**. See: `docs/OPENCLAW_SKILL_MANIFEST_SCHEMA.md`. ## Optional: execution sandbox (Docker) 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). ## Files - `scripts/run_audit_json.sh` — main JSON audit runner - `scripts/hostile_audit.py` — prompt-injection/persistence/dependency hygiene scanner - `scripts/security_audit.sh` — convenience wrapper (always returns JSON, never non-zero) - `openclaw-skill.json` — machine-readable intent/permissions manifest

Frequently asked questions

Security Audit