ci-security-scanning-with-strix

ci-security-scanning-with-strix is a skill for Claude Code, Codex from usestrix/strix. It costs 140 tokens per session (2,228 once invoked), scanned B, original, Apache-2.0.

A workflow for adding Strix security tests to CI/CD, the automated process that checks and delivers code. It supports GitHub Actions, GitLab CI, and other pipelines, with tests focused on the code changed in a pull request.

In plain words
What is it for?
Use it to configure managed or self-hosted scans, post findings on pull requests, and upload SARIF results to code-scanning tools.
Why use it?
It catches validated security vulnerabilities before changes are merged and can make the build fail when issues are found.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to configure managed or self-hosted scans, post findings on pull requests, and upload SARIF results to code-scanning tools.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/usestrix/strix/ci-security-scanning-with-strix
About the project

Strix is an open-source penetration-testing tool that uses autonomous AI agents to inspect applications, exploit vulnerabilities, and validate findings with working proofs of concept. Developers and security teams use it for application security testing, bug-bounty research, remediation guidance, reporting, and automated checks in development pipelines.

usestrix/strix · 70,805 stars · on GitHub · strix.ai

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add usestrix/strix --skill ci-security-scanning-with-strix
Clone the repo
git clone --depth 1 https://github.com/usestrix/strix

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for ci-security-scanning-with-strix

README.md
[![agentmods](https://agentmods.dev/badge/skills/usestrix/strix/ci-security-scanning-with-strix/github.svg)](https://agentmods.dev/skills/usestrix/strix/ci-security-scanning-with-strix)
Your own site
<a href="https://agentmods.dev/skills/usestrix/strix/ci-security-scanning-with-strix"><img src="https://agentmods.dev/badge/skills/usestrix/strix/ci-security-scanning-with-strix/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for ci-security-scanning-with-strix

Your own site · 80×15
<a href="https://agentmods.dev/skills/usestrix/strix/ci-security-scanning-with-strix"><img src="https://agentmods.dev/badge/skills/usestrix/strix/ci-security-scanning-with-strix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 140 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,228 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 4 Oct 2026
  • Snyk warn 4 Oct 2026
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 6 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Supply Chain · line 44
    Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.
    Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
  • high Supply Chain · line 91
    Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.
    Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
  • high Supply Chain · line 128
    Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.
    Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
  • high Tool Misuse · line 44
    Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.
    Fix: Limit tool chaining depth and validate the output of each tool before passing it to the next. Require explicit user approval for multi-step chains.
  • high Tool Misuse · line 91
    Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.
    Fix: Limit tool chaining depth and validate the output of each tool before passing it to the next. Require explicit user approval for multi-step chains.
  • high Tool Misuse · line 128
    Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.
    Fix: Limit tool chaining depth and validate the output of each tool before passing it to the next. Require explicit user approval for multi-step chains.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00140 $0.02228
Opus 5.5 $0.00056 $0.00891
Sonnet 5.5 $0.00028 $0.00446
Haiku 4.5 $0.00014 $0.00223

Measured 18d ago against content hash f8e1dd61721d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

ci-security-scanning-with-strix scanned grade B with 2 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 18d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Downloads and executes remote codemediumSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

run: curl -sSL https://strix.ai/install | bash

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

run: curl -sSL https://strix.ai/install | bash
Origin

Copies of this mod

1 near-identical copy found in the catalogue:

skills/ci-security-scanning-with-strix/SKILL.md · 150 lines

How it starts

The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Set up Strix in CI/CD

You can gate PRs two ways — pick based on the environment, or combine them:

  • 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 post as PR comments and land in the team dashboard. Best when you want zero CI maintenance, central tracking, or your runners lack Docker. See "Managed platform" below and the managed-pentesting-with-strix skill.
  • Self-hosted OSS CLI in your runner — run a diff-scoped scan as a pipeline step. Fully in your infra, free (BYO LLM key), no external account. Requires Docker on the runner. Best for air-gapped/self-hosted CI or when you do not want scans leaving your environment.

Both fail the build on validated findings and both emit SARIF 2.1.0, so you can start with one and add the other later.


Option A — Self-hosted OSS CLI in the runner

Run a diff-scoped Strix scan on every PR: only changed files are tested, quick mode keeps it fast, and exit code 2 fails the build when validated vulnerabilities are found.

GitHub Actions

Create .github/workflows/security.yml:

name: Security Scan

on:
  pull_request:

jobs:
  strix-scan:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0   # required for diff-scope resolution

      - name: Install Strix
        run: curl -sSL https://strix.ai/install | bash

      - name: Run Security Scan
        env:
          STRIX_LLM: ${{ secrets.STRIX_LLM }}
          LLM_API_KEY: ${{ secrets.LLM_API_KEY }}
        run: strix -n -t ./ --scan-mode quick --max-budget 10

      # Don't fail open: a run that hits the hard budget stop exits 0 but leaves
      # run.json status "stopped", not "completed". Enforce completion explicitly.
      # This does not catch an agent that wrapped up early on a budget *warning*
      # (it still calls finish_scan and records "completed"), so size the budget.
      - name: Fail unless the scan completed
        run: |
          run_json=$(ls -t strix_runs/*/run.json | head -1)
          status=$(jq -r .status "$run_json")
          if [ "$status" != "completed" ]; then
            echo "Strix run status is '$status' — the scan did not complete (likely budget exhausted). Raise --max-budget." >&2
            exit 1
          fi

Read the full file on GitHub · 150 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 18d ago Changed f8e1dd61721d
  2. 1mo ago Changed · +13 lines 715bdf9ce1f3
  3. 1mo ago First seen · 137 lines · 140 tokens per session scan B 25758e5fd256

Subscribe to this mod's changes

ci-security-scanning-with-strix is a skill published in the GitHub repository usestrix/strix (70,805 stars, last pushed today), licensed Apache-2.0. It adds 140 tokens to every session and 2,228 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it B with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.