SKILLEMALL.ai
GitHub ↗ RU Sign in

BF sast-configuration

Configure Static Application Security Testing (SAST) tools for automated vulnerability detection in application code. Use when setting up security scanning, implementing DevSecOps practices, or automating code vulnerability detection.

modbender/skill-library-mcp Agent Skills author: modbender MIT 1 file body ≈ 1 560 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Configure Static Application Security Testing (SAST) tools for automated vulnerability detection in application code.

As a process F 47/100 · Will not run — References files that are not bundled: references/semgrep-rules.md, references/sonarqube-config.md, references/codeql-setup.md

AnalyzerGitHubSoftware developmentInfrastructureSecuritytype 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
B
89/100
safety, quality, tests
Safety 60%
99
Quality 40%
75
Run on models
none yet
Process rating
F
47/100
Will not run
References files that are not bundled: references/semgrep-rules.md, references/sonarqube-config.md, references/codeql-setup.md
Tools and files w 18
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. 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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Risky intent intent-offensive-security SKILL.md:20
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - You only need DAST or manual penetration testing guidance

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

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: references/semgrep-rules.md
  • warning missing-ref reference to a missing file: references/sonarqube-config.md
  • warning missing-ref reference to a missing file: references/codeql-setup.md
  • warning missing-ref reference to a missing file: assets/semgrep-config.yml
  • warning missing-ref reference to a missing file: assets/sonarqube-settings.xml
  • warning missing-ref reference to a missing file: scripts/run-sast.sh
  • warning missing-ref reference to a missing file: ../owasp-top10-checklist/SKILL.md
  • warning missing-ref reference to a missing file: ../container-security/SKILL.md
  • warning missing-ref reference to a missing file: ../dependency-scanning/SKILL.md

Process rating: all ten parameters 47/100

Will not run. References files that are not bundled: references/semgrep-rules.md, references/sonarqube-config.md, references/codeql-setup.md
  • 0Tools and files. 9 referenced file(s) missing: references/semgrep-rules.md, references/sonarqube-config.md, references/codeql-setup.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 7 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 60Result and completion. Output format stated, no completion criterion
  • 85Steps. 81 steps, 2 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1560 tokens
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 16 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 234: enough signal without eating the budget
  • +4Structure: 30 headings
  • +3Step-by-step instructions: 81 items
  • +3Output format is stated explicitly
  • +4Has examples (6 code blocks)

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