docs/integrations/coding-agents.mdx
Strix is built to be driven by AI coding agents. Install the official agent skills and your agent knows how to run pentests, remediate findings, and wire Strix into CI.
Works with any agent that supports the open SKILL.md standard — Claude Code, Cursor, Codex, Gemini CLI, OpenCode, and dozens more:
npx skills add usestrix/strix
| Skill | What your agent learns |
|---|---|
penetration-testing-with-strix | Run headless scans against code, URLs, domains, or IPs — self-hosted CLI or managed cloud — with budget caps, and read the results |
managed-pentesting-with-strix | Drive the managed app.strix.ai platform over REST — no local Docker or LLM key needed |
fix-security-vulnerabilities-with-strix | Triage findings, fix root causes, and re-run Strix to verify each fix |
ci-security-scanning-with-strix | Add PR security scanning to GitHub Actions or any CI (self-hosted CLI or managed app) |
Install a single skill with npx skills add usestrix/strix --skill penetration-testing-with-strix, or use one without installing:
npx skills use usestrix/strix@penetration-testing-with-strix | claude
Both use the same engine and produce the same validated findings and SARIF, so agents can pick per situation or combine them:
managed-pentesting-with-strix skill has the full flow.Everything an agent needs is machine-readable:
strix -n runs without the TUI and exits with 0 (clean), 1 (error), or 2 (vulnerabilities found).https://app.strix.ai/api/v1 (scans, vulnerabilities, assets, PR reviews, schedules, webhooks) with bearer tokens and scopes.vulnerabilities.json, vulnerabilities.csv, findings.sarif (SARIF 2.1.0), and per-finding Markdown under strix_runs/<run-name>/; the cloud exposes the same as JSON plus SARIF export.--max-budget and --max-turns give agents hard cost/time caps.AGENTS.md — the repository's agent guide with a quick reference.llms.txt — this documentation is indexed at docs.strix.ai/llms.txt and fully exported at docs.strix.ai/llms-full.txt; every page is also available as Markdown by appending .md to its URL.Once the skills are installed, prompts like these just work:
Pentest this repo with Strix (quick mode, $10 budget) and summarize the findings.
Fix all critical and high findings from the last Strix run, then re-scan to verify.
Add Strix security scanning to our GitHub Actions so every PR gets tested.