跳到正文
cccskills
免费在 GitHub 公开

application-security-testing

Plan and coordinate Strix security assessments across source code, running applications, APIs, and continuous integration pipelines. Combine findings into one prioritized remediation plan based on demonstrated impact, removing duplicates and documenting gaps in test coverage.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

Application security testing (AppSec) across a whole product with Strix — decide which asset needs which test (source code, running web app, API, CI pipeline), run it, and turn the results into a ranked remediation plan. Autonomous agents exploit and prove each issue instead of emitting static-analysis alerts, so the plan is ordered by what is actually reachable. Use when the user asks for an application security review or audit, an appsec assessment, vulnerability scanning across their stack, a security review before a launch or a customer security questionnaire, or does not yet know which kind of security test they need.

集成工具Docker
查看安装方法

适用场景

  • Choosing suitable security tests for a product
  • Planning a security assessment before launch
  • Combining findings into a prioritized remediation plan
  • Preparing an assessment for customer security questionnaires

包含的文件(1)

  • SKILL.md4.5 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Application security testing

Entry point for "make my application secure" requests, where the target is not yet a single URL or repo. The job here is to pick the right test per asset, run it, and produce one ranked plan — not to run everything at maximum depth.

Install, LLM setup, all CLI flags, and the managed-cloud path live in the penetration-testing-with-strix skill. Read it first if strix --version fails. For a run with no Docker and no LLM key, the same binary drives the managed platform: strix cloud login, then strix cloud scans start ... (details in managed-pentesting-with-strix).

Only test assets the user owns or is authorized to test. Confirm authorization before the first run, and prefer staging over production, because the agents send real exploit payloads and can change data.

1. Map the assets

Ask (or read from the repo) and write the answers down before scanning:

  • Source — one repo, a monorepo, several services? Which languages/frameworks?
  • Running environments — is there a staging deployment? A public production site? A local dev server only?
  • APIs — REST, GraphQL, gRPC? Is there an OpenAPI/GraphQL schema?
  • Authentication — can you get two test accounts in different tenants? Most high-impact bugs need them.
  • Constraints — out-of-scope paths, whether production may be touched, budget and wall-clock limits.

If there is no staging environment and production is off limits, say so early. A code-only review is still valuable, but it cannot prove exploitability against a live app.

2. Pick the right test per asset

AssetSkill to use
Repository or working treefind-security-vulnerabilities-in-code
Live web app or staging siteweb-app-penetration-testing
REST/GraphQL/gRPC APIapi-security-testing
Assessment mapped to OWASP categoriesowasp-top-10-testing
Every pull request, continuouslyci-security-scanning-with-strix
No Docker, no LLM key, or a report an auditor will acceptmanaged-pentesting-with-strix

Those skills carry the flags, credential handling, and result-reading details. Do not duplicate their instructions here.

Sequence for a first assessment:

  1. Review the code. It is the cheapest run and it maps the authorization model.
  2. Pentest staging with credentials, and pass the repo as a second target so the agents keep source context.
  3. Add CI scanning, so later regressions are caught without another manual pass.

Run one asset at a time and read each report before starting the next. Findings from the code review make the live run sharper.

3. Consolidate into one plan

Findings arrive per run in strix_runs/<run>/. Merge them into a single list and rank by proven impact, not by scanner severity:

  1. Validated exploits reachable without authentication.
  2. Validated cross-tenant or privilege-escalation issues.
  3. Validated issues needing an authenticated account.
  4. Unproven observations (configuration, dependency, and hardening notes) — flag as such, and never present them as confirmed vulnerabilities.

Deduplicate: the same root cause often surfaces in both the code review and the live pentest.

4. Be honest about coverage

State plainly what was not tested — assets with no staging environment, categories a black-box run cannot reach (logging and alerting, supply-chain integrity, insecure design), and any run that hit its budget or turn cap before finishing. Check run.json status and cost against --max-budget for each run. An empty result set from a truncated scan is not a clean bill of health.

Then remediate with fix-security-vulnerabilities-with-strix, which re-runs Strix against each fix to prove the exploit no longer works.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Test REST, GraphQL, and gRPC APIs with Strix using schemas, credentials, and example data. Investigate authorization flaws, excessive data exposure, and other API risks, then verify findings with requests that reproduce the issue.

中文简介正在准备中。当前显示英语简介。

  • Testing an API from its specification
  • Checking data access across tenants
  • Verifying restrictions on administrator routes
usestrix/strix7万2026年10月18日 更新

Set up Strix security checks in CI/CD to test pull request changes, report verified vulnerabilities, and gate merges. Covers both a CLI running on your own infrastructure and a managed service with pull request comments.

中文简介正在准备中。当前显示英语简介。

  • Check pull request changes for vulnerabilities before merging
  • Add Strix scans to GitHub Actions or GitLab CI
  • Choose between managed reviews and scans on your own runners
usestrix/strix7万2026年10月18日 更新

Review source code with Strix to trace data flow and authorization checks, then test suspected vulnerabilities in a running environment. Receive proven findings with exploit examples and code locations, while keeping unconfirmed observations clearly identified.

中文简介正在准备中。当前显示英语简介。

  • Reviewing a repository for security vulnerabilities
  • Checking authorization logic in a specific service
  • Reviewing security risks introduced by a branch
usestrix/strix7万2026年10月18日 更新

Turn Strix vulnerability findings into focused code fixes, prioritized by severity. Address root causes, rerun security scans and original exploit examples, and report the changes and verification results for each issue.

中文简介正在准备中。当前显示英语简介。

  • Fixing vulnerabilities reported by Strix
  • Prioritizing remediation by severity
  • Retesting original exploits after code changes
usestrix/strix7万2026年10月18日 更新

Run security tests for web apps, APIs, and source code on Strix Cloud without local Docker or an LLM key. Register targets, review findings in a team dashboard, export results, and configure recurring scans or PR reviews.

中文简介正在准备中。当前显示英语简介。

  • Running security tests without local Docker
  • Tracking vulnerability status across a team
  • Scheduling scans and starting PR security reviews
usestrix/strix7万2026年10月18日 更新

Assess an application against OWASP Top 10:2025 risk categories using Strix. Get findings backed by working exploit examples, organized by category, with clear explanations of what was tested and what remains unassessed.

中文简介正在准备中。当前显示英语简介。

  • Assessing an app against OWASP Top 10:2025
  • Testing access controls across users and tenants
  • Organizing proven vulnerabilities by risk category
usestrix/strix7万2026年10月18日 更新

查看 usestrix 的全部技能

报告此技能的问题