[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M785P9A3FE2YVS2K3BRGWR58":3,"skill-same:01M785P9A3FE2YVS2K3BRGWR58":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M785P9A3FE2YVS2K3BRGWR58","application-security-testing",null,"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.","freeforall1932-design\u002Fskills-repo","freeforall1932-design","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F300004558?v=4","01M7857WA4YZEAY92CZK81AS79","free for all","01M7857WAYPXNBAZFGX3FYT8FD",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Ffreeforall1932-design\u002Fskills-repo\u002Fblob\u002Fmain\u002Fone-skill\u002Fupstream\u002Fstrix\u002Fskills\u002Fapplication-security-testing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: application-security-testing\ndescription: 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.\nlicense: Apache-2.0\nmetadata:\n  author: usestrix\n  homepage: https:\u002F\u002Fdocs.strix.ai\n---\n\n# Application security testing\n\nEntry 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.\n\nInstall, 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**).\n\nOnly 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.\n\n## 1. Map the assets\n\nAsk (or read from the repo) and write the answers down before scanning:\n\n- **Source** — one repo, a monorepo, several services? Which languages\u002Fframeworks?\n- **Running environments** — is there a staging deployment? A public production site? A local dev server only?\n- **APIs** — REST, GraphQL, gRPC? Is there an OpenAPI\u002FGraphQL schema?\n- **Authentication** — can you get two test accounts in different tenants? Most high-impact bugs need them.\n- **Constraints** — out-of-scope paths, whether production may be touched, budget and wall-clock limits.\n\nIf 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.\n\n## 2. Pick the right test per asset\n\n| Asset | Skill to use |\n| --- | --- |\n| Repository or working tree | **find-security-vulnerabilities-in-code** |\n| Live web app or staging site | **web-app-penetration-testing** |\n| REST\u002FGraphQL\u002FgRPC API | **api-security-testing** |\n| Assessment mapped to OWASP categories | **owasp-top-10-testing** |\n| Every pull request, continuously | **ci-security-scanning-with-strix** |\n| No Docker, no LLM key, or a report an auditor will accept | **managed-pentesting-with-strix** |\n\nThose skills carry the flags, credential handling, and result-reading details. Do not duplicate their instructions here.\n\nSequence for a first assessment:\n\n1. Review the code. It is the cheapest run and it maps the authorization model.\n2. Pentest staging with credentials, and pass the repo as a second target so the agents keep source context.\n3. Add CI scanning, so later regressions are caught without another manual pass.\n\nRun one asset at a time and read each report before starting the next. Findings from the code review make the live run sharper.\n\n## 3. Consolidate into one plan\n\nFindings arrive per run in `strix_runs\u002F\u003Crun>\u002F`. Merge them into a single list and rank by **proven impact**, not by scanner severity:\n\n1. Validated exploits reachable without authentication.\n2. Validated cross-tenant or privilege-escalation issues.\n3. Validated issues needing an authenticated account.\n4. Unproven observations (configuration, dependency, and hardening notes) — flag as such, and never present them as confirmed vulnerabilities.\n\nDeduplicate: the same root cause often surfaces in both the code review and the live pentest.\n\n## 4. Be honest about coverage\n\nState 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.\n\nThen remediate with **fix-security-vulnerabilities-with-strix**, which re-runs Strix against each fix to prove the exploit no longer works.\n","# Application security testing\n\nEntry 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.\n\nInstall, 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**).\n\nOnly 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.\n\n## 1. Map the assets\n\nAsk (or read from the repo) and write the answers down before scanning:\n\n- **Source** — one repo, a monorepo, several services? Which languages\u002Fframeworks?\n- **Running environments** — is there a staging deployment? A public production site? A local dev server only?\n- **APIs** — REST, GraphQL, gRPC? Is there an OpenAPI\u002FGraphQL schema?\n- **Authentication** — can you get two test accounts in different tenants? Most high-impact bugs need them.\n- **Constraints** — out-of-scope paths, whether production may be touched, budget and wall-clock limits.\n\nIf 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.\n\n## 2. Pick the right test per asset\n\n| Asset | Skill to use |\n| --- | --- |\n| Repository or working tree | **find-security-vulnerabilities-in-code** |\n| Live web app or staging site | **web-app-penetration-testing** |\n| REST\u002FGraphQL\u002FgRPC API | **api-security-testing** |\n| Assessment mapped to OWASP categories | **owasp-top-10-testing** |\n| Every pull request, continuously | **ci-security-scanning-with-strix** |\n| No Docker, no LLM key, or a report an auditor will accept | **managed-pentesting-with-strix** |\n\nThose skills carry the flags, credential handling, and result-reading details. Do not duplicate their instructions here.\n\nSequence for a first assessment:\n\n1. Review the code. It is the cheapest run and it maps the authorization model.\n2. Pentest staging with credentials, and pass the repo as a second target so the agents keep source context.\n3. Add CI scanning, so later regressions are caught without another manual pass.\n\nRun one asset at a time and read each report before starting the next. Findings from the code review make the live run sharper.\n\n## 3. Consolidate into one plan\n\nFindings arrive per run in `strix_runs\u002F\u003Crun>\u002F`. Merge them into a single list and rank by **proven impact**, not by scanner severity:\n\n1. Validated exploits reachable without authentication.\n2. Validated cross-tenant or privilege-escalation issues.\n3. Validated issues needing an authenticated account.\n4. Unproven observations (configuration, dependency, and hardening notes) — flag as such, and never present them as confirmed vulnerabilities.\n\nDeduplicate: the same root cause often surfaces in both the code review and the live pentest.\n\n## 4. Be honest about coverage\n\nState 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.\n\nThen remediate with **fix-security-vulnerabilities-with-strix**, which re-runs Strix against each fix to prove the exploit no longer works.\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"homepage":26},"usestrix","https:\u002F\u002Fdocs.strix.ai","main","fd69413366e5700923cdaf27e816a6342375913e","one-skill\u002Fupstream\u002Fstrix\u002Fskills\u002Fapplication-security-testing","https:\u002F\u002Fgithub.com\u002Ffreeforall1932-design\u002Fskills-repo","https:\u002F\u002Fgithub.com\u002Ffreeforall1932-design","shipping product noone need or known for myself feel free to use it if useful","2026-11-02 13:54:04",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add freeforall1932-design\u002Fskills-repo --skill application-security-testing",{"tool":40,"command":41},"bunx","bunx skills add freeforall1932-design\u002Fskills-repo --skill application-security-testing",{"tool":43,"command":44},"pnpm","pnpm dlx skills add freeforall1932-design\u002Fskills-repo --skill application-security-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffreeforall1932-design\u002Fskills-repo\u002Fblob\u002Fmain\u002Fone-skill\u002Fupstream\u002Fstrix\u002Fskills\u002Fapplication-security-testing\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M785QNETYHDCDXFE8AV3KFH9","web-app-penetration-testing","Pentest a web app or website end to end — black-box testing of a live URL, staging environment, or local dev server that finds and exploits real vulnerabilities (auth bypass, broken access control, IDOR, injection, XSS, SSRF, business logic) and proves each one with a working proof-of-concept instead of a signature match. Runs with Strix, either the self-hosted open-source CLI or the managed app.strix.ai cloud. Use when the user asks to pentest, hack, security-test, or audit their web app, website, web application, or staging site.","https:\u002F\u002Fgithub.com\u002Ffreeforall1932-design\u002Fskills-repo\u002Fblob\u002Fmain\u002Fone-skill\u002Fupstream\u002Fstrix\u002Fskills\u002Fweb-app-penetration-testing\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M785QFE2RMXMRHPHE0R7M3YW","penetration-testing-with-strix","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\u002Faccess-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.","https:\u002F\u002Fgithub.com\u002Ffreeforall1932-design\u002Fskills-repo\u002Fblob\u002Fmain\u002Fone-skill\u002Fupstream\u002Fstrix\u002Fskills\u002Fpenetration-testing-with-strix\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M785Q8Y2VM6W3KJ5QK5P6VF6","owasp-top-10-testing","Test an application against the OWASP Top 10 with Strix — autonomous AI agents that attempt real exploits for each category of the current OWASP Top 10:2025 (broken access control including SSRF, security misconfiguration, software supply chain failures, cryptographic failures, injection, insecure design, authentication failures, integrity failures, logging and alerting failures, mishandling of exceptional conditions) and report only what they could actually prove, mapped back to the category with a proof-of-concept. Also covers the OWASP API Security Top 10 (2023). Use when the user asks for an OWASP Top 10 assessment, OWASP compliance testing, or a security review mapped to OWASP categories.","https:\u002F\u002Fgithub.com\u002Ffreeforall1932-design\u002Fskills-repo\u002Fblob\u002Fmain\u002Fone-skill\u002Fupstream\u002Fstrix\u002Fskills\u002Fowasp-top-10-testing\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M785Q24K39ZEYMXENVAYKPME","managed-pentesting-with-strix","Run a managed pentest of a web app, API, repository, or local workspace on the app.strix.ai platform with the `strix cloud` CLI or REST API — no local Docker or LLM key needed. Safely review and upload local source, register assets, launch and poll scans, triage vulnerabilities, export SARIF, download compliance reports, start PR reviews, buy credits, and set up schedules or webhooks. Use for managed, continuous, scheduled, team-tracked, or sandboxed-agent security testing.","https:\u002F\u002Fgithub.com\u002Ffreeforall1932-design\u002Fskills-repo\u002Fblob\u002Fmain\u002Fone-skill\u002Fupstream\u002Fstrix\u002Fskills\u002Fmanaged-pentesting-with-strix\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M785PW8EPMNN5SH43RVGHFFE","fix-security-vulnerabilities-with-strix","Fix security vulnerabilities found by a Strix pentest (open-source CLI or app.strix.ai cloud) — triage by severity, patch the root cause rather than the symptom, and re-run Strix to prove each fix actually closes the exploit. Handles injection, XSS, SSRF, broken access control, IDOR, and other validated findings. Use after a Strix scan reports findings, or when the user asks to remediate, patch, or fix security issues from a strix_runs report, vulnerabilities.json, findings.sarif, or a cloud scan.","https:\u002F\u002Fgithub.com\u002Ffreeforall1932-design\u002Fskills-repo\u002Fblob\u002Fmain\u002Fone-skill\u002Fupstream\u002Fstrix\u002Fskills\u002Ffix-security-vulnerabilities-with-strix\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M785PP7C1N489KVZYX002FEM","find-security-vulnerabilities-in-code","Find security vulnerabilities in a codebase or repository with Strix — a white-box AI security review that reads your source, reasons about the actual data flow and authorization model, then exploits what it finds in a live sandbox so every reported issue has a working proof-of-concept instead of a noisy static-analysis alert. Covers injection, XSS, SSRF, broken access control and IDOR, insecure deserialization, secrets in code, unsafe dependencies, and business-logic flaws. Use when the user asks to security-scan, security-review, or audit their code, repo, or pull request for vulnerabilities.","https:\u002F\u002Fgithub.com\u002Ffreeforall1932-design\u002Fskills-repo\u002Fblob\u002Fmain\u002Fone-skill\u002Fupstream\u002Fstrix\u002Fskills\u002Ffind-security-vulnerabilities-in-code\u002FSKILL.md",[],[]]