Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
smartchainark avatar

Skill Security Audit

  • 502 installs
  • 9 repo stars
  • Updated February 9, 2026
  • smartchainark/skill-security-audit

skill-security-audit is a Claude Code skill whose Python scanner detects malicious patterns in installed agent skills using 13 detectors for backdoors, credential theft, and exfiltration.

About

skill-security-audit is a checker skill that scans installed Claude and OpenClaw agent skills for malicious patterns before they run. Its bundled Python scanner auto-discovers skill directories and applies thirteen detectors for backdoors, credential theft, data exfiltration, obfuscation, and supply-chain attacks, then reports findings ranked by severity. Developers use it to vet community skills before install or merge and to guide remediation and credential rotation on critical hits. The detectors are based on SlowMist's ClawHub analysis of over 472 malicious skills and the scanner is pure Python with zero dependencies.

  • Scans agent skills for malicious patterns
  • 13 detectors for backdoors and exfiltration
  • Based on SlowMist ClawHub threat intelligence

Skill Security Audit by the numbers

  • 502 all-time installs (skills.sh)
  • +1 installs in the week ending Aug 5, 2026 (Skillselion tracking)
  • Ranked #509 of 2,203 Security skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

skill-security-audit capabilities & compatibility

Free, pure Python with zero dependencies and no API key.

Capabilities
security audit · malicious pattern detection · supply chain scan · credential theft detection · ioc matching
Use cases
security audit
Runs
Runs locally
Pricing
Free
From the docs

What skill-security-audit says it does

Detect malicious patterns in AI Agent skills — 13 detectors for backdoors, credential theft, data exfiltration, and supply-chain attacks.
SKILL.md
Based on SlowMist's analysis of 472+ malicious skills on ClawHub platform.
SKILL.md
npx skills add https://github.com/smartchainark/skill-security-audit --skill skill-security-audit

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs502
repo stars9
Last updatedFebruary 9, 2026
Repositorysmartchainark/skill-security-audit

How do I know an installed or candidate agent skill is not a backdoor, credential stealer, or supply-chain attack?

security-audit

Who is it for?

Developers vetting community Claude or OpenClaw skills before install or merge who want an automated scan for backdoors, credential theft, and supply-chain attacks.

Skip if: Auditing general application source code, since it targets agent skill files and known malicious patterns rather than OWASP web vulnerabilities.

When should I use this skill?

The user asks for a security audit, skill check, or scan of installed skills for malicious or supply-chain patterns.

What you get

All discovered skills are scanned and findings are grouped by skill and ranked CRITICAL to LOW with recommended removal or credential-rotation actions.

  • Severity-ranked audit report
  • Remediation and credential-rotation guidance

By the numbers

  • 13 detection categories
  • Based on 472+ malicious skills
  • 5-step audit workflow

Files

SKILL.mdMarkdownGitHub ↗

Skill Security Audit

Detect malicious patterns in installed Claude and OpenClaw skills. Based on SlowMist's analysis of 472+ malicious skills on ClawHub platform.

Triggers

Use this skill when the user mentions: 安全审计, security audit, skill 检查, 技能安全, scan skills, supply chain security, 扫描技能, 恶意检测, malicious skill, skill 安全扫描

Quick Audit Workflow

When the user requests a security audit, follow these 5 steps:

Step 1: Run the Scanner

python3 ~/.claude/skills/skill-security-audit/scripts/skill_audit.py

This auto-discovers and scans all skills in:

  • ~/.claude/skills/
  • ~/.openclaw/workspace/skills/
  • Extra directories from ~/.openclaw/openclaw.jsonskills.load.extraDirs

Step 2: Analyze Results

Read the scanner output. Findings are grouped by skill and sorted by severity:

SeverityMeaningAction Required
CRITICALKnown malicious IOC match, credential theft, or download-and-executeImmediate removal and credential rotation
HIGHObfuscation, persistence mechanisms, privilege escalationManual review required, likely malicious
MEDIUMSuspicious patterns (Base64, network calls, high entropy)Review context — may be legitimate
LOWSocial engineering naming, informationalNote for awareness

Step 3: Report to User

Present findings in this format:

## Audit Summary
- Skills scanned: N
- Files scanned: N
- CRITICAL: N | HIGH: N | MEDIUM: N | LOW: N

## Critical/High Findings (if any)
For each finding:
- Skill name and file path
- What was detected and why it's dangerous
- Recommended action

## Medium/Low Findings (if any)
Brief summary, noting which are likely false positives

Step 4: Recommend Actions

For CRITICAL findings: 1. Read references/remediation-guide.md for incident response steps 2. Guide user through credential rotation if credential theft was detected 3. Help quarantine the malicious skill

For HIGH findings: 1. Help user manually review the flagged code 2. Determine if the pattern is legitimate or malicious in context

Step 5: Follow Up

  • Offer to scan a specific skill in detail: python3 skill_audit.py --path /path/to/skill
  • Offer to explain any finding in depth using references/threat-patterns.md

Scanner Command Reference

# Scan all discovered skills
python3 ~/.claude/skills/skill-security-audit/scripts/skill_audit.py

# Scan a single skill directory
python3 ~/.claude/skills/skill-security-audit/scripts/skill_audit.py --path /path/to/skill

# JSON output (for programmatic use)
python3 ~/.claude/skills/skill-security-audit/scripts/skill_audit.py --json

# Filter by minimum severity
python3 ~/.claude/skills/skill-security-audit/scripts/skill_audit.py --severity high

# Disable colored output
python3 ~/.claude/skills/skill-security-audit/scripts/skill_audit.py --no-color

# Use custom IOC database
python3 ~/.claude/skills/skill-security-audit/scripts/skill_audit.py --ioc-db /path/to/ioc.json

Exit codes: 0 = clean, 1 = low/medium risk, 2 = high risk, 3 = critical, 4 = scanner error

13 Detection Categories

DetectorWhat It FindsSeverity
Base64DetectorEncoded strings >50 chars (excluding data:image)MEDIUM→HIGH
DownloadExecDetectorcurl\bash, wget\
IOCMatchDetectorKnown malicious IPs, domains, URLs, file hashesCRITICAL
ObfuscationDetectoreval/exec with non-literal args, hex encoding, chr() chainsHIGH
ExfiltrationDetectorZIP+upload combos, sensitive directory enumerationHIGH
CredentialTheftDetectorosascript password dialogs, keychain access, SSH key readingCRITICAL
PersistenceDetectorcrontab, launchd, systemd, shell profile modificationHIGH
PostInstallHookDetectornpm postinstall, pip setup.py cmdclassHIGH→CRITICAL
HiddenCharDetectorZero-width characters, Unicode bidi overridesMEDIUM
EntropyDetectorShannon entropy >5.5 on long linesMEDIUM
SocialEngineeringDetectorcrypto/wallet/airdrop/security-update namingLOW→MEDIUM
NetworkCallDetectorsocket, http, urllib, requests, fetch, curl, wgetMEDIUM
PrivilegeEscalationDetectorsudo, chmod 777, setuid, admin group modificationHIGH

Understanding Confidence Scores

Each finding includes a confidence score (0-100):

  • 80-100: Very likely a genuine threat
  • 50-79: Suspicious, manual review recommended
  • 30-49: Possible false positive, check context
  • <30: Informational, low confidence

Manual Review Checklist

When the scanner flags something, also check:

1. Source verification — Is the skill from an official/verified source? Check author reputation. 2. Permission scope — Does the skill request more permissions than its stated functionality needs? 3. Script audit — Read all .sh, .py, .js files. Look for obfuscation, unexpected network calls. 4. Dependency check — Run npm audit or pip-audit if the skill has package dependencies. 5. Changelog review — Were suspicious changes introduced in a recent update?

Updating the IOC Database

The IOC database is at scripts/ioc_database.json. To add new indicators:

1. Edit the JSON file following the existing schema 2. Run the scanner to verify your new IOCs are detected 3. Update references/ioc-database.md to keep the human-readable version in sync

Reference Documents

For detailed information, read these files as needed:

  • references/ioc-database.md — Full IOC list with context and attribution
  • references/threat-patterns.md — 9 attack patterns in detail (two-stage payload, Base64 backdoor, password phishing, etc.)
  • references/remediation-guide.md — Step-by-step incident response (quarantine, credential rotation, persistence cleanup, reporting)

Related skills

How it compares

Prefer a fully documented skill-security-auditor with explicit injection and script scan tables when public audit checklists are required.

FAQ

How many detectors does skill-security-audit run?

Thirteen detectors covering Base64, download-and-execute, IOC matches, obfuscation, exfiltration, credential theft, persistence, post-install hooks, and more.

What is the detection based on?

SlowMist's analysis of over 472 malicious skills on the ClawHub platform, matched against a bundled IOC database.

Securityauditappsecsecrets

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.