DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to block insecure code in pull requests with Strix

Run a quick Strix scan in GitHub Actions on every pull request to catch vulnerabilities before merge.

Authorization notice. Strix is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Credentials. The workflow depends on LLM_API_KEY stored as a GitHub secret, so limit who can read or change repository secrets.

Remote script. The workflow installs Strix with curl piped to bash, so pin or review the installer if your CI policy requires it.

Who it is forA dev team lead who wants a security gate in CI so insecure changes do not reach production.

The problemSecurity review often happens too late, after code is merged and deployed.

The outcomeA pull request workflow that runs a headless Strix scan and fails when vulnerabilities are found.

What you need first

  • Docker installed and running
  • An LLM API key from a supported provider, or a ChatGPT Plus/Pro subscription sign-in
  • The application source directory or a target URL you are authorized to test
  • A GitHub repository with Actions enabled, if you want the CI workflow

Steps

  1. Save the README's strix-penetration-test YAML as a workflow file in .github/workflows/. (inferred, check the README)
  2. Add STRIX_LLM and LLM_API_KEY as repository secrets in GitHub.
  3. Open a pull request so the workflow runs strix -n -t ./ --scan-mode quick.
  4. Check the Actions log for the printed findings; the run exits with a non-zero code when vulnerabilities are found.

Prompt for your agent

Add the strix-penetration-test GitHub Actions workflow from the usestrix/strix README to <target-repo>, using the STRIX_LLM and LLM_API_KEY secrets. Open a pull request and report the workflow result. Verify that the workflow step runs `strix -n -t ./ --scan-mode quick` and that a non-zero exit is reported when findings exist.

Caveat. The README says quick reviews in pull requests are scoped to changed files, which is why the checkout uses fetch-depth 0.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for usestrix/strix and "Block insecure code in pull requests"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer