SKILLEMALL.ai
GitHub ↗ RU Sign in

AB clawsec-scanner

Automated vulnerability scanner for agent platforms. Performs dependency scanning (npm audit, pip-audit), multi-database CVE lookup (OSV, NVD, GitHub Advisory), SAST analysis (Semgrep, Bandit), and agent-specific DAST hook execution testing for OpenClaw hooks.

LeoYeAI/openclaw-master-skills Agent Skills author: LeoYeAI MIT 22 files · 1 script body ≈ 3 972 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Automated vulnerability scanner for agent platforms.

As a process B 67/100 · Nearly there — weak spots: when it triggers, running it twice

AnalyzerGitHubSoftware developmentSecurityAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
99
Quality 40%
76
Run on models
none yet
Process rating
B
67/100
Nearly there
When it triggers w 12
20
Running it twice w 4
30
Failures and branches w 10
50
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 1

✓ No critical or high findings

Medium and low: 1
  • low Secrets in code secret-high-entropy-token SKILL.md:136
    High-entropy token-like string (may be an id, hash or a credential)
    MCow…XJX+GYGv…m6A=

Files scanned: 16. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "homepage"
  • note frontmatter-key unknown frontmatter key "clawdis"
  • note edit-residue the text marks something as outdated (lines 444): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 67/100

  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 4 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (bash, python, node) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 107 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3972 tokens
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 12 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +1No license
  • +2Single-language instructions
  • +3Description length 260: enough signal without eating the budget
  • +4Structure: 34 headings
  • +3Step-by-step instructions: 107 items
  • +3Output format is stated explicitly
  • +4Has examples (15 code blocks)
  • +3All 7 scripts are documented

Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.