fix-security-vulnerabilities-with-strix SKILL.md skillA
fix-security-vulnerabilities-with-strix from usestrix/strix is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add usestrix/strix/fix-security-vulnerabilities-with-strix@git:20260901.42baa7cPins git:20260901.42baa7c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- usestrix/strix
- Path
skills/fix-security-vulnerabilities-with-strix/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260901.42baa7c, committed Sep 1, 2026
- First version recorded
- Aug 7, 2026
- Size
- 5,997 bytes
- Repository stars
- 74,096
- License
- Apache-2.0
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…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Fix Strix findings and verify Turn validated Strix findings into minimal, correct fixes — and prove they work by re-scanning. ## 1. Triage Get the findings from wherever the scan ran: - **OSS CLI** — artifacts in `strix_runs/<run-name>/`: - `vulnerabilities/*.md` — one finding per file: description, severity, PoC steps or script, affected code locations, remediation guidance. - `vulnerabilities.json` — the same findings as JSON (ids, severity, CWE/CVE, `code_locations` with `fix_before`/`fix_after` suggestions when available). - **Cloud (app.strix.ai)** — pull findings with the CLI: `strix cloud vulns list --scan-id <scan-id> --json` (or `strix cloud scans get <scan-id> --json | jq '.vulnerabilities'`, or `strix cloud vulns list --severity critical` org-wide). Each finding carries `severity, cwe, endpoint, method, impact, technical_analysis, poc_description, poc_script_code` and, for code findings, `code_file`/`code_diff`/`code_before`/`code_after`. After a fix is verified, mark it with `strix cloud vulns update <id> --status fixed`. See the **managed-pentesting-with-strix** skill for `strix cloud login` and scopes. …
Read the whole file at its exact version.
How to install
mdr add usestrix/strix/fix-security-vulnerabilities-with-strix@sha256:bb1b351fd60c91e4The line at the top of this page pins the label git:20260901.42baa7c, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_lvbrvvscwjy2vs4h)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Aug 7, 2026 and Sep 1, 2026, about one every 13 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260901.42baa7c latest | 2026-09-01 | 42baa7c | 5,997 B | A | view · diff |
| git:20260820.9099710 | 2026-08-20 | 9099710 | 5,783 B | A | view · diff |
| git:20260807.f8a8801 | 2026-08-07 | f8a8801 | 5,774 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5997 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
usestrix/strix · 74,096 stars · license Apache-2.0 · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lvbrvvscwjy2vs4h GET https://markdownregistry.com/api/v1/resolve?ref=usestrix/strix/fix-security-vulnerabilities-with-strix GET https://markdownregistry.com/api/v1/blob/bb1b351fd60c91e4875207f3fe4f35774ff5194261a00aea9f4752e459f24a9f
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.