fix-finding skillA
fix-finding is agent-read markdown (skill) from cowork-os/cowork-os: Use when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Fix Finding ## Objective Turn a security finding into a minimal, validated code change when the issue still exists. If the issue is already fixed, prove that with focused validation and report that no code change was needed. The result should include the fix if one was needed, focused regression tests or another repeatable validation check, proof that normal behavior still works, and proof that the original issue no longer reproduces. ## Inputs Start by extracting any available finding details: - title and affected component - vulnerable source, sink, or broken control - attacker-controlled input - expected security invariant - impact and required preconditions - existing PoC, reproducer, test, or validation evidence - files and line references If a critical field is missing, inspect the repository to fill it from code evidence. Ask the user only when the fix would otherwise require guessing a product policy or security invariant. ## Note on Runtime Validation Use this guidance whenever reproducing the finding, running tests, or validating the fix: - Try hard to make runtime validation run before falling back to code inspection. …
Read the whole file at its exact version.
How to install
mdr add cowork-os/cowork-os/fix-finding@git:20260606.a4dececmdr add cowork-os/cowork-os/fix-finding@sha256:41b9a5b26839b98dPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_ecnq7n7pnli5vn6q)
1 badge views in 30 days
Versions
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 (7731 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
cowork-os/cowork-os · 459 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ecnq7n7pnli5vn6q GET https://markdownregistry.com/api/v1/resolve?ref=cowork-os/cowork-os/fix-finding GET https://markdownregistry.com/api/v1/blob/41b9a5b26839b98d95f71ee10a7097fc5d27d309abbcabdd1371af824552e093
Your agent 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.