跳到主内容
智客 ZICQ

技能库 智客分类:安全测试 penetration-testing-with-strix

Penetration Testing With Strix

Pentest a web app,API,codebase,寄存器,URL,域名,或有Strix的IP——自主的AI穿入测试,利用并证明脆弱性(OWASP Top 10及外-注射,XSS,SSF,auth/access-control缺陷,IDOR,业务逻辑),而不只是标出它们. 使用开源CLI或通过所管理的app.strix.ai云进行自我托管,并用概念开发的验证结果返回(Markdown,JSON,CSV,SARIF). 当用户要求测试、入侵、安全扫描、安全审计或在应用程序、API、网站或repo中找到漏洞时使用.

9071 安装量

官方网址:作者主页

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

Pentest a web app,API,codebase,寄存器,URL,域名,或有Strix的IP——自主的AI穿入测试,利用并证明脆弱性(OWASP Top 10及外-注射,XSS,SSF,auth/access-control缺陷,IDOR,业务逻辑),而不只是标出它们. 使用开源CLI或通过管理下的app.strix.ai云进行自我托管,并使用概念开发验证结果返回(Markdown、JSON、CSV、SARIF)

何时用

用户要求测试、入侵、安全扫描、安全审计,或在应用程序、API、网站或Repo中找到漏洞

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Run a Strix pentest、Which one? (decide, do not default)、Option A — Open-source CLI (self-hosted)、Prerequisites、Running a scan、Local code (white-box)。

文件分析

文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。

官方 description(原文)

Pentest a web app, API, codebase, repository, URL, domain, or IP with Strix — autonomous AI penetration testing that exploits and proves vulnerabilities (OWASP Top 10 and beyond — injection, XSS, SSRF, auth/access-control flaws, IDOR, business logic) instead of just flagging them. Runs self-hosted with the open-source CLI or via the managed app.strix.ai cloud, and returns validated findings with proof-of-concept exploits (Markdown, JSON, CSV, SARIF). Use when the user asks to pentest, hack, security-scan, security-audit, or find vulnerabilities in an app, API, website, or repo.

Run a Strix pentestWhich one? (decide, do not default)Option A — Open-source CLI (self-hosted)PrerequisitesRunning a scanLocal code (white-box)Deployed app / API (black-box)Repo + deployed app together (best coverage)Focused testing with credentials or scope hintsAPI spec as a first-class target (OpenAPI/Swagger or a Postman collection export)Many targets from a file, one per lineGive the agents a file to work with (wordlist, spec, notes) without making it a target

· 许可:Apache-2.0

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
penetration-testing-with-strix
description
Pentest a web app, API, codebase, repository, URL, domain, or IP with Strix — autonomous AI penetration testing that exploits and proves vulnerabilities (OWASP Top 10 and beyond — injection, XSS, SSRF, auth/access-control flaws, IDOR, business logic) instead of just flagging them. Runs self-hosted with the open-source CLI or via the managed app.strix.ai cloud, and returns validated findings with proof-of-concept exploits (Markdown, JSON, CSV, SARIF). Use when the user asks to pentest, hack, security-scan, security-audit, or find vulnerabilities in an app, API, website, or repo.
许可
Apache-2.0
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「penetration-testing-with-strix」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-a5b5fd3532d7d71a-%E7%94%A8-Strix-%E8%BF%9B%E8%A1%8C%E7%A9%BF%E9%80%8F%E6%B5%8B%E8%AF%95.html
请存为 .cursor/skills/penetration-testing-with-strix/SKILL.md 或 .claude/skills/penetration-testing-with-strix/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/usestrix/strix' --list

npx skills add 'https://github.com/usestrix/strix' --skill 'penetration-testing-with-strix'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: penetration-testing-with-strix description: Pentest a web app, API, codebase, repository, URL, domain, or IP with Strix — autonomous AI penetration testing that exploits and proves vulnerabilities (OWASP Top 10 and beyond — injection, XSS, SSRF, auth/access-control flaws, IDOR, business logic) instead of just flagging them. Runs self-hosted with the open-source CLI or via the managed app.strix.ai cloud, and returns validated findings with proof-of-concept exploits (Markdown, JSON, CSV, SARIF). Use when the user asks to pentest, hack, security-scan, security-audit, or find vulnerabilities in an app, API, website, or repo. license: Apache-2.0 metadata: author: usestrix homepage: https://docs.strix.ai --- # Run a Strix pentest Strix runs autonomous AI pentesting agents that dynamically exploit a target and only report findings validated with a working proof-of-concept. There are **two ways to run it, built on the same engine and producing the same findings** — pick per situation, and mix them freely: - **Open-source CLI** (self-hosted) — runs on your machine in a Docker sandbox with your own LLM key. Free, fully local, BYO-LLM, air-gap capable. Docs: [docs.strix.ai](https://docs.strix.ai). - **Managed cloud** — runs on Strix's infrastructure, driven from the same CLI (`strix cloud ...`) or the REST API at `https://app.strix.ai/api/v1`. No Docker, no LLM key, no local compute; adds team dashboards, scheduling, PR reviews, downloadable PDF/DOCX reports (Enterprise plan), and internal-network connectors. Docs: [docs.app.strix.ai](https://docs.app.strix.ai). Full workflow in the **managed-pentesting-with-strix** skill. ## Which one? (decide, do not default) Choose honestly based on the situation — neither is "better": | Situation | Prefer | |---|---| | No Docker available, or a sandboxed/hosted agent/CI environment | **Cloud** | | User has no LLM key / does not want to pay per-token or manage models | **Cloud** | | Team visibility, shareable dashboard, scheduled/continuous scans, PR reviews, downloadable PDF/DOCX report (Enterprise) | **Cloud** | | Scanning internal/private infrastructure not reachable from your machine | **Cloud** (network connector) | | Source must never leave local infra (privacy/air-gap), or fully offline | **OSS CLI** | | Free / one-off / local dev-loop scan, Docker already present | **OSS CLI** | | BYO or self-hosted LLM, or a specific model not offered by the platform | **OSS CLI** | | CI: runner already has Docker and you want a self-contained gate | **OSS CLI** | | CI: no Docker, or you want results tracked centrally | **Cloud** | **Mix them:** use the OSS CLI for the fast local dev-loop while writing/fixing code, and the Cloud for the authoritative, team-visible scan + report + tracking; or gate PRs with the OSS CLI in CI while the Cloud runs scheduled deep scans and PR reviews across the org. Both emit the same SARIF 2.1.0, so findings line up across environments. If unsure and the user has (or will create) an app.strix.ai account, prefer **Cloud** — it avoids all local-infra friction. If they want zero signup / full local control, use the **OSS CLI**. --- # Option A — Open-source CLI (self-hosted) ## Prerequisites 1. **Docker running** — check with `docker info`. The first scan pulls the sandbox image automatically. 2. **Strix installed** — check with `strix --version`. Install if missing: ```bash curl -sSL https://strix.ai/install | bash # or: pipx install strix-agent ``` 3. **LLM configured** — two environment variables: ```bash export STRIX_LLM="openai/gpt-5.4" # any LiteLLM model id (openai/..., anthropic/..., openrouter/...) export LLM_API_KEY="" ``` Ask the user for these if unset. Never hardcode or commit keys. ## Running a scan Always use `-n` (non-interactive/headless) — the default TUI blocks agents. Always set `--max-budget` unless the user says otherwise. ```bash # Local code (white-box) strix -n -t ./ --scan-mode standard --max-budget 10 # Deployed app / API (black-box) strix -n -t https://staging.example.com --max-budget 20 # Repo + deployed app together (best coverage) strix -n -t https://github.com/org/app -t https://staging.example.com # Focused testing with credentials or scope hints strix -n -t https://app.example.com \ --instruction "Use credentials [email protected]:pass123. Focus on IDOR and auth bypass." # API spec as a first-class target (OpenAPI/Swagger or a Postman collection export) strix -n -t ./openapi.yaml -t https://api.staging.example.com # Many targets from a file, one per line strix -n --target-list ./targets.txt --max-budget 30 # Give the agents a file to work with (wordlist, spec, notes) without making it a target strix -n -t https://staging.example.com --workspace-file ./wordlist.txt --max-budget 20 ``` A local path passed with `-t` is mounted into the sandbox **writable** — the agents can read and modify it, so point at a clean checkout, not uncommitted work you care about. Key flags: | Flag | Meaning | |---|---| | `-t, --target` | URL, repo URL, local path, domain, IP, OpenAPI/Postman spec, or `postman://`. Repeatable. | | `--target-list PATH` | File of targets, one per line (`#` comments allowed). Repeatable, combines with `-t`. | | `-n, --non-interactive` | Headless, exits on completion. Required for agents. | | `-m, --scan-mode` | `quick` (minutes) / `standard` (~30 min) / `deep` (hours, default). | | `--instruction` / `--instruction-file` | Credentials, focus areas, scope rules. | | `--workspace-file PATH[:DEST]` | Copy a file from this machine into `/workspace` before the scan, for a wordlist, a spec, or notes. Repeatable. | | `--max-budget USD` | Hard LLM spend cap; scan wraps up cleanly at the limit. | | `--max-turns N` | Per-agent turn cap (default 500). | | `--resume RUN_NAME` | Resume a prior run from `strix_runs/`, with its agent history and targets. Cannot be combined with `-t`. | | `--scope-mode` | For code targets: `auto` (diff-scope in CI/headless), `diff` (force changed files only), `full` (whole tree). | | `--diff-base REF` | Branch or commit that `diff` scope compares against. Defaults to the repo's default branch. | Scans take minutes (`quick`) to hours (`deep`). Run them in the background and poll for completion rather than blocking. ### Exit codes (headless) - `0` — finished with no validated vulnerabilities **in what was analyzed** - `1` — fatal error (missing env vars, Docker down, bad config) - `2` — vulnerabilities found A `0` is not proof of full coverage: if `--max-budget`/`--max-turns` is reached before the scan completes, it wraps up early and still exits `0`. When you need assurance the scan finished, give it enough budget and check `strix_runs//run.json`: a hard budget stop leaves `status: "stopped"`, but an agent that wrapped up early on a budget *warning* still calls `finish_scan` and records `"completed"` — so also sanity-check the run's cost against `--max-budget` and the report's stated coverage before treating a clean result as full coverage. ### Reading results Artifacts land in `strix_runs//`: | File | Contents | |---|---| | `penetration_test_report.md` | Executive report — read this first. | | `vulnerabilities/*.md` | One file per validated finding, with PoC and remediation. | | `vulnerabilities.json` / `vulnerabilities.csv` | All findings as structured JSON / CSV index. | | `findings.sarif` | SARIF 2.1.0 for GitHub code scanning / ASPM ingestion. | | `run.json` | Run metadata, status, targets, usage/cost. | --- # Option B — Managed cloud (no local infra) The same `strix` binary drives the managed platform. Every command starts with `strix cloud`. Full details — asset registration, source uploads, reports, PR reviews, schedules, webhooks, and billing — are in the **managed-pentesting-with-strix** skill. Minimal flow: ```bash # 1. Sign in (device flow — the user confirms a code in the browser; this also # creates the account and workspace when needed) strix cloud login # If you need specific scopes, request them with --scopes: # strix cloud login --scopes scans:read scans:write assets:read assets:write \ # vulnerabilities:read billing:read billing:write # 2. Register and verify the target domain (verification prints a DNS record for the user) strix cloud domains add --domain staging.example.com --asset-type web_app strix cloud domains verify # 3. Launch and wait strix cloud scans start --engagement-type live_test --domain-ids --wait # 4. Read validated findings strix cloud vulns list --severity critical ``` For a local repository, `strix cloud scans start --source .` uploads the working tree (needs `uploads:write`) and infers a code review. When credits run out, `strix cloud billing topup` starts an agent-payable Stripe challenge — the managed skill covers the payment flow. Output is JSON when stdout is not a terminal, so the commands compose in scripts. The raw REST API works too (`https://app.strix.ai/api/v1`, org-scoped bearer token — see [docs.app.strix.ai](https://docs.app.strix.ai)). If Docker or local prerequisites are not already satisfied, use this path instead of trying to install infra. --- ## Reporting & next steps Summarize findings by severity (critical/high/medium/low/info) and include the PoC evidence. To remediate and verify fixes (via either path), use the **fix-security-vulnerabilities-with-strix** skill. To wire scanning into CI/CD, use the **ci-security-scanning-with-strix** skill. ## Safety Only scan targets the user owns or is authorized to test. The Cloud platform enforces domain verification before external scans; for the OSS CLI, confirm authorization yourself if the target looks like third-party infrastructure.

相关技能

安全测试

Skill Vetter

人工智能特工的安全第一技能审查。 在安装来自 ClawdHub, GitHub 或其他来源的任何技能之前使用 。 检查红旗,许可范围,可疑图案.

安全测试

Moltguard

MoltGuard——由OpenGuardrails担任OpenClaw保安. 安装 MoltGuard 以保护你和你的人类免受迅速注射、数据过滤和恶意命令的影响。 资料来源:https://github.com/openguardrails/openguardrails/tre…

安全测试

Security Auditor

用于审查安全漏洞代码,实施认证流,审计OWASP Top 10,配置CORS/CSP头,处理秘密,输入验证,SQL注射预防,XSS保护,或任何与安全相关的代码审查.

安全测试

Skill Vetter

安装任何AI代理技能前的安全审查协议. 红旗侦取入证盗取,疏通密码,放出. 风险分类:低/中/高/高。 编制结构化审查报告。 不先运行此功能, 绝不安装不信任的技能 .