agentleFS
vodolaz095vodolaz095/go-mcp-smtp/skills/vuln-scan/SKILL.md

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

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
  1. Distinctive:

    When a vulnerability is found in a dependency, update it using:

    line 19
  2. Very specific:

    Ensure required tools are available (make tools)

    line 35
  3. Very specific:

    Ensure dependencies are downloaded (make deps)

    line 36
  4. Very specific:

    Run vulnerability scan (make vuln)

    line 37
  5. Distinctive:

    Check the module's release history for the minimum version that fixes the vulnerability

    line 39
  6. Very specific:

    Update the module using go get with the appropriate version

    line 40
  7. Very specific:

    Run make deps to update go.mod and go.sum

    line 41
  8. Distinctive:

    Always verify that updating a dependency does not break existing functionality

    line 52
  9. Very specific:

    Consider running tests (make test) after updating dependencies

    line 53

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 vuln

Fix Vulnerable Dependencies

When a vulnerability is found in a dependency, update it using:

go get -u <module>@latest

Or 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

  1. Ensure required tools are available (make tools)
  2. Ensure dependencies are downloaded (make deps)
  3. Run vulnerability scan (make vuln)
  4. Identify vulnerable modules from the report
  5. Check the module's release history for the minimum version that fixes the vulnerability
  6. Update the module using go get with the appropriate version
  7. Run make deps to update go.mod and go.sum
  8. Re-run make vuln to verify the vulnerability is resolved

Requirements

  • govulncheck must 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.