SKILLEMALL.ai
GitHub ↗ RU Sign in

DD vuln-scanner

Audit trending repos for real security vulnerabilities and disclose responsibly - scan and route findings (PVR / dependency PR), re-submit queued advisories, and send armed email disclosures

aeonfun/aeon Agent Skills author: aeonfun 2 files body ≈ 20 528 tokens Open the sourcegithub.com↗ analyzed 79 min ago

Audit trending repos for real security vulnerabilities and disclose responsibly - scan and route findings (PVR / dependency PR), re-submit queued advisories…

As a process D 47/100 · Unfinished process — References files that are not bundled: url, scripts/stage-vuln-scanner.sh, scripts/skill_mode.sh

AnalyzerGitHubSoftware developmentData and analyticstype and topics are labelled automatically from the skill text
Runs in: 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) OpenClaw Goose OpenCode
JSON
Technical rating
D
76/100
safety, quality, tests
Safety 60%
97
Quality 40%
45
Run on models
none yet
Process rating
D
47/100
Unfinished process
References files that are not bundled: url, scripts/stage-vuln-scanner.sh, scripts/skill_mode.sh
Tools and files w 18
0
Result and completion w 14
0
Execution cost w 6
10
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.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  3. The text references files that are not there: add them or drop the references.
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 · 3

✓ No critical or high findings

Medium and low: 3
  • low Risky intent intent-offensive-security SKILL.md:332
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    reviewable, no exploit chain to redact. A PR is the appropriate channel for
  • low Risky intent intent-offensive-security SKILL.md:576
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)
    | **Fuzz crash in a dependency** | **Public PR to the dependency's repo** (fix, not just a report, if it's small and matches their conventions) | DoS-only, no exploit chain to redact — see A3.5 case 2
    detector

A further 1 matches are quotations in this security skill's documentation and are not counted as findings.

Files scanned: 2. 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")
  • warning body-long SKILL.md body ≈ 20528 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: url
  • warning missing-ref reference to a missing file: scripts/stage-vuln-scanner.sh
  • warning missing-ref reference to a missing file: scripts/skill_mode.sh
  • warning missing-ref reference to a missing file: scripts/stage-deploy-uni-hook.sh
  • note edit-residue the text marks something as outdated (lines 42, 46, 47, 325, 329, 347): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 47/100

Will not run. References files that are not bundled: url, scripts/stage-vuln-scanner.sh, scripts/skill_mode.sh
  • 0Tools and files. 4 referenced file(s) missing: url, scripts/stage-vuln-scanner.sh, scripts/skill_mode.sh
  • 0Result and completion. Does not say what the result is
  • 10Execution cost. Instruction body is 20528 tokens: crowds the task out of the window
  • 30Inputs and preconditions. Does not say what the process needs to start
  • 50When it triggers. No condition that starts the skill
  • 85Steps. 120 steps, 1 vague phrases
  • 100Failures and branches. 7 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 10 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (8 tags): a typed call is more reliable

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)
  • +3Output format is not stated: the model decides each time
  • -5TODO / placeholder text left in the skill
  • +1No license
  • +2Single-language instructions
  • +3Description length 190: enough signal without eating the budget
  • +4Structure: 43 headings
  • +3Step-by-step instructions: 120 items
  • +4Has examples (39 code blocks)

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