agentleFS
Sign inStart free
kaandgnshkaandgnsh/Claude-Blue/skills/container-security/image-scanning/SKILL.md

image-scanning

Skill0 starsChanged 11 days agoMITView on GitHub

Scan container images for vulnerabilities, secrets, misconfigurations and malware with Trivy, Grype or registry-native scanners; choose minimal base images; gate builds; and continuously rescan registries and running workloads. Use when building or approving container images, triaging image CVE reports, or setting registry admission policy.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Prefer minimal images: distroless, Chainguard/Wolfi, Alpine (musl caveats), scratch for static binaries.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Container Image Scanning

Scan

trivy image --severity HIGH,CRITICAL --ignore-unfixed ghcr.io/org/app@sha256:<digest>
trivy image --scanners vuln,secret,misconfig --format sarif -o trivy.sarif ghcr.io/org/app:1.4.2
grype ghcr.io/org/app@sha256:<digest> --only-fixed --fail-on high
trivy k8s --report summary cluster          # scan workloads running in a cluster (Trivy k8s mode)

Registry-native: ECR enhanced scanning (Inspector), Azure Defender for Containers, GCP Artifact Analysis, Harbor (Trivy).

Triage

  1. Base image vs. app layer: trivy image --format json shows the layer/package; most OS CVEs are fixed by rebuilding on an updated base.
  2. Fixable? --ignore-unfixed to focus effort; track unfixed criticals with exceptions.
  3. Reachability/runtime relevance: package present but binary never executed (e.g., perl in a Go service image) → remove it with a smaller base rather than debating.
  4. KEV/EPSS prioritization (vuln-prioritization).

Base image strategy

Prefer minimal images: distroless, Chainguard/Wolfi, Alpine (musl caveats), scratch for static binaries; pin by digest; rebuild on a schedule (weekly) and on critical base CVEs; maintain an approved base-image list.

Gates

CI: fail on fixable critical (and KEV) in new images. Registry: block pulls of images with critical findings or no signature (artifact-signing). Runtime: rescan running images daily — new CVEs appear for old images.

Output

Image@digest | Base | Critical/High (fixable) | KEV | Secrets | Misconfig | Decision | Owner

Related skills

dockerfile-hardening, sbom-vulnerability-analysis, artifact-signing, release-gate

References

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.

Check your setup, free