vuln-scan
Skill0 starsChanged 3 months agoMITView on GitHub
This skill scans the codebase for known vulnerabilities using govulncheck via the make vuln target. It also provides guidance on fixing vulnerable dependencies by upgrading them with go get according to semver. When a vulnerability is found in a dependency, update it using: Or to update to a specific version that fixes the issue (respecting semver): Then run make deps to synchronize the module changes.
- Installs packages
9 other projects use a version of this.
Adopted by
Most recently taken up by
- Q00/ouroborostheir own version, first seen Oct 25, 2026
- air-gapped/skillstheir own version, first seen Oct 19, 2026
- jaskaranhundal/usap-skillstheir own version, first seen Sep 5, 2026
- epicsagas/epic-harnesstheir own version, first seen Sep 4, 2026
- scadastrangelove/rust-in-peacetheir own version, first seen Aug 3, 2026
- anthropics/defending-code-reference-harnesstheir own version, first seen Jul 16, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- anthropics/defending-code-reference-harness★ 7.5ksame name
- Q00/ouroboros★ 6.4ksame name
- scadastrangelove/rust-in-peace★ 25same name
- epicsagas/epic-harness★ 20same name
- air-gapped/skills★ 6same name
- jaskaranhundal/usap-skills★ 4same name
- mykaarma/kaarma-skills★ 4same name
- flintfromthebasement/skills★ 1same name
- IvandoNascimento/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 3 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
When a vulnerability is found in a dependency, update it using:
- Very specific: line 35
Ensure required tools are available (make tools)
- Very specific: line 36
Ensure dependencies are downloaded (make deps)
- Very specific: line 37
Run vulnerability scan (make vuln)
- Distinctive: line 39
Check the module's release history for the minimum version that fixes the vulnerability
- Very specific: line 40
Update the module using go get with the appropriate version
- Very specific: line 41
Run make deps to update go.mod and go.sum
- Distinctive: line 52
Always verify that updating a dependency does not break existing functionality
- Very specific: line 53
Consider running tests (make test) after updating dependencies
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
vuln-scan
Description
This skill scans the codebase for known vulnerabilities using govulncheck via the make vuln target. It also provides guidance on fixing vulnerable dependencies by upgrading them with go get according to semver.
Usage
Scan for Vulnerabilities
make tools
make deps
make vulnFix Vulnerable Dependencies
When a vulnerability is found in a dependency, update it using:
go get -u <module>@latestOr to update to a specific version that fixes the issue (respecting semver):
go get <module>@<fixed_version>Then run make deps to synchronize the module changes.
Workflow
- Ensure required tools are available (
make tools) - Ensure dependencies are downloaded (
make deps) - Run vulnerability scan (
make vuln) - Identify vulnerable modules from the report
- Check the module's release history for the minimum version that fixes the vulnerability
- Update the module using
go getwith the appropriate version - Run
make depsto updatego.modandgo.sum - Re-run
make vulnto verify the vulnerability is resolved
Requirements
govulncheckmust be installed (go install golang.org/x/vuln/cmd/govulncheck@latest)- Go 1.26+
- Internet access to fetch vulnerability database and module updates
Notes
- Always verify that updating a dependency does not break existing functionality
- Consider running tests (
make test) after updating dependencies - For production applications, prefer pinning to a specific patch version over
@latest
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

