security-scanner

name	Security Scanner
description	Scan AI agent skills for security vulnerabilities, dangerous code patterns, and undeclared permissions. Three-layer analysis: dependency CVE scanning via OSV.dev, static code analysis, and permission auditing. Returns structured JSON risk report. Use when the user asks to scan a skill for security issues, check for vulnerabilities, audit permissions, or assess skill safety.
metadata	{"requires":{"env":["CLAW0X_API_KEY"]}}

Security Scanner

Scan AI agent skills for security vulnerabilities across three layers: dependency CVEs, dangerous code patterns, and undeclared permissions. Returns a structured JSON risk report with an overall score (0�?00).

Free to use. This skill costs nothing. Just sign up at claw0x.com, create an API key, and start calling. No credit card, no wallet top-up required.

How It Works �?Under the Hood

This skill runs a three-layer security analysis pipeline. No LLM involved �?pure deterministic scanning logic.

Layer 1: Dependency CVE Scanning

Dependencies are extracted from package.json (npm) or requirements.txt (PyPI) and queried against the OSV.dev batch vulnerability database.

• Fetches dependency manifests from the target repository
• Queries all packages in a single batch request to OSV.dev
• Classifies each vulnerability by severity: critical, high, medium, low
• Score contribution: critical +25, high +15, medium +8, low +3 (capped at 50)

Layer 2: Static Code Analysis

Source files (.ts, .js, .py) are scanned line-by-line against 8 pre-compiled regex rules:

Rule	What It Detects	Severity
EXEC_EVAL	eval(), new Function(), vm.runInContext	critical
SHELL_INJECT	child_process.exec, execSync, shell template literals	critical
ENV_LEAK	process.env.* in response/return context	high
DATA_EXFIL	fetch() / axios.post to non-whitelisted domains	high
HARDCODED_CRED	API key/token/password string literals	high
UNSAFE_IMPORT	require() / import from HTTP URLs	medium
FS_OVERREACH	Read/write to /etc, ~/.ssh, ~/.aws	medium
INSECURE_NET	http:// (non-HTTPS) in fetch/request calls	low

• Score contribution: critical +20, high +12, medium +5, low +2 (capped at 40)

Layer 3: Permission Auditing

The SKILL.md frontmatter allowed-tools field is cross-referenced against actual code behavior detected by the static analyzer.

• Parses declared permissions from SKILL.md YAML frontmatter
• Maps code findings to permission categories (e.g., child_process.exec �?Bash(*))
• Reports any permissions detected in code but not declared in frontmatter
• Score contribution: +5 per undeclared permission (capped at 10)

Risk Score

The three layer scores are summed into a total risk score (0�?00):

Score Range	Risk Level
0�?0	Low
21�?0	Medium
51�?00	High

Three Input Modes

You can scan a skill using any of these three modes (mutually exclusive �?provide exactly one):

Mode 1: GitHub Repo URL

Provide a public GitHub repository URL. The scanner fetches dependency files, source code, and SKILL.md automatically.

{ "repo_url": "https://github.com/owner/repo" }

Mode 2: Claw0x Skill Slug

Provide a skill slug from the Claw0x platform. The scanner looks up the associated repo URL and proceeds with the standard scan.

{ "skill_slug": "validate-email" }

Mode 3: Direct Code Submission

Submit code directly along with optional dependency and SKILL.md data. No GitHub fetching needed.

{
  "code": "import os\nos.system('rm -rf /')",
  "dependencies": { "requests": "2.28.0" },
  "skill_md": "---\nname: my-skill\nallowed-tools: Bash(curl *)\n---"
}

Prerequisites

This is a free skill. Just get an API key:

1. Sign up at claw0x.com
2. Go to Dashboard �?API Keys �?Create Key
3. Store the key securely using one of these methods:
   • Add CLAW0X_API_KEY to your agent's secure environment variables
   • Use your platform's secret manager (e.g. GitHub Secrets, Vercel env vars, AWS Secrets Manager)
   • Use a .env file that is excluded from version control via .gitignore

Security note: Never embed API keys in prompts, source code, or version-controlled files.

No credit card or wallet balance needed.

When to Use

• Agent pipeline needs to vet a third-party skill before installing
• Developer wants to self-check a skill before publishing to Claw0x
• Platform review pipeline needs automated security assessment
• User asks "is this skill safe?", "scan for vulnerabilities", "check skill security"

Input

Provide exactly one of the three input modes:

Field	Type	Required	Description
repo_url	string	one of three	GitHub repo URL (https://github.com/{owner}/{repo})
skill_slug	string	one of three	Claw0x skill slug (1�?00 chars)
code	string	one of three	Source code to scan (max 500KB)
dependencies	object	no	Package name �?version map (used with code mode)
skill_md	string	no	SKILL.md content for permission auditing (used with code mode)

Output Fields

Field	Type	Description
overall_risk	string	Risk level: low, medium, or high
risk_score	number	Numeric risk score (0�?00)
input_mode	string	Which input mode was used
repo_url	string | null	Repository URL if applicable
dependency_scan.packages_scanned	number	Number of packages checked
dependency_scan.vulnerabilities	array	Found CVEs (max 20)
dependency_scan.vulnerability_counts	object	Count by severity level
code_scan.findings	array	Dangerous code patterns found (max 50)
code_scan.finding_counts	object	Count by severity level
code_scan.rules_checked	number	Number of rules applied
permission_audit.declared_permissions	array	Permissions from SKILL.md
permission_audit.detected_permissions	array	Permissions found in code
permission_audit.undeclared_risks	array	Detected but not declared
recommendations	array	Actionable fix suggestions
scanned_at	string	ISO 8601 scan timestamp
scan_duration_ms	number	Total scan time in milliseconds

Example

Input:

{
  "skill": "security-scanner",
  "input": {
    "code": "const { exec } = require('child_process');\nexec(userInput);",
    "dependencies": { "lodash": "4.17.20" }
  }
}

Output:

{
  "overall_risk": "high",
  "risk_score": 62,
  "input_mode": "direct",
  "repo_url": null,
  "dependency_scan": {
    "packages_scanned": 1,
    "vulnerabilities": [
      {
        "id": "GHSA-jf85-cpcp-j695",
        "summary": "Prototype Pollution in lodash",
        "severity": "high",
        "package_name": "lodash",
        "package_version": "4.17.20"
      }
    ],
    "vulnerability_counts": {
      "critical": 0,
      "high": 1,
      "medium": 0,
      "low": 0
    }
  },
  "code_scan": {
    "findings": [
      {
        "rule_id": "SHELL_INJECT",
        "name": "Shell injection",
        "severity": "critical",
        "file": "input.ts",
        "line": 1,
        "match": "require('child_process')",
        "description": "Shell command execution detected �?risk of injection attacks"
      }
    ],
    "finding_counts": {
      "critical": 1,
      "high": 0,
      "medium": 0,
      "low": 0
    },
    "rules_checked": 8
  },
  "permission_audit": {
    "declared_permissions": [],
    "detected_permissions": ["Bash(*)"],
    "undeclared_risks": ["Bash(*)"]
  },
  "recommendations": [
    "Critical: Shell injection pattern detected �?avoid passing unsanitized input to child_process",
    "High: lodash@4.17.20 has known vulnerabilities �?upgrade to latest version",
    "Undeclared permission: Bash(*) detected in code but not declared in SKILL.md"
  ],
  "scanned_at": "2025-01-15T10:30:00.000Z",
  "scan_duration_ms": 1250
}

Error Codes

• 400 — No valid input provided (need repo_url, skill_slug, or code)
• 401 — Invalid or missing API key
• 404 — Skill slug not found in catalog
• 500 — Scan failed (not billed)

Pricing

Free. Apply for an API key and use it at no cost. No credit card required.