SKILLEMALL.ai
GitHub ↗ RU Sign in

BC ci-security-scanning-with-strix

Add security scanning to CI/CD with Strix — GitHub Actions, GitLab CI, or any pipeline — so every pull request gets a diff-scoped AI pentest that blocks vulnerable code before it merges, with results as PR comments and SARIF uploaded to code scanning. Covers both the self-hosted open-source CLI (runs in your runner) and the managed app.strix.ai platform (GitHub/GitLab app or API, no runner infra). Use when the user asks to add security scanning, SAST/DAST, pentesting, vulnerability checks, or automated security review to their CI pipeline, pre-merge gate, or PR workflow.

usestrix/strix Agent Skills author: usestrix Apache-2.0 1 file body ≈ 2 067 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Add security scanning to CI/CD with Strix — GitHub Actions, GitLab CI, or any pipeline — so every pull request gets a diff-scoped AI pentest that blocks…

As a process C 51/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches

ProcedureGitHubGitLabDockerSoftware developmentInfrastructureSecuritytype 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
B
90/100
safety, quality, tests
Safety 60%
94
Quality 40%
85
Run on models
none yet
Process rating
C
51/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

    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 · 6

    ✓ No critical or high findings

    Medium and low: 6
    • low Risky intent intent-offensive-security SKILL.md:3
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      description: Add security scanning to CI/CD with Strix — GitHub Actions, GitLab CI, or any pipeline — so every pull request gets a diff-scoped AI pentest that blocks vulnerable code before it merges,
    • low Risky intent intent-offensive-security SKILL.md:14
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      - **Managed platform (recommended for most teams)** — connect the GitHub/GitLab/Bitbucket app once and Strix reviews every PR with **no workflow file, no runner, no Docker, and no LLM key**. Results p
    • low Dangerous commands cmd-pipe-to-shell SKILL.md:44
      Downloads and executes remote code from an unrecognised host (pipe to shell) (documentation of a security skill; the skill's own vendor host)
      run: curl -sSL https://strix.ai/install | bash
      security skillvendor-host
    • low Dangerous commands cmd-pipe-to-shell SKILL.md:91
      Downloads and executes remote code from an unrecognised host (pipe to shell) (documentation of a security skill; the skill's own vendor host)
      curl -sSL https://strix.ai/install | bash
      security skillvendor-host
    • low Dangerous commands cmd-pipe-to-shell SKILL.md:128
      Downloads and executes remote code from an unrecognised host (pipe to shell) (documentation of a security skill; the skill's own vendor host)
      curl -sSL https://strix.ai/install | bash
      security skillvendor-host
    • low Risky intent intent-offensive-security SKILL.md:147
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)
      Full CLI coverage (PR reviews, scans, SARIF export, schedules) is in the **managed-pentesting-with-strix** skill.
      detector

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

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 51/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 30Running it twice. 2 mutating operations with no state check
    • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
    • 70When it triggers. States when to use, but not when not to
    • 100Steps. 9 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2067 tokens
    • 100Progress reporting. Reports progress

    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
    • +2Single-language instructions
    • +3Description length 577: enough signal without eating the budget
    • +4Structure: 6 headings
    • +3Step-by-step instructions: 9 items
    • +4Has examples (5 code blocks)
    • +1License stated

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