agentleFS
Sign inStart free
ByronScottJonesByronScottJones/Agents/skills/build-and-scan-container-image/SKILL.md

build-and-scan-container-image

Skill7 starsChanged 2 months agoMITView on GitHub

Use when building, validating, scanning, or generating an SBOM for a container image. Checks Dockerfile safety, base images, secrets, non-root execution, vulnerabilities, reproducibility, and immutable tagging.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

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

    Check base-image support, multi-stage builds, secret leakage, user identity, ports, health checks, and reproducible dependency inputs.

    line 26
  2. Distinctive:

    Verify runtime user, exposed capabilities, and immutable digest.

    line 30
  3. Distinctive:

    Never place secrets in Dockerfiles, layers, arguments, or labels.

    line 35
  4. Very specific:

    Never push latest as the only release identifier.

    line 36
  5. Distinctive:

    Default to no registry mutation.

    line 37

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

Build and Scan Container Image

Implement containers.md as a build-and-release gate.

Parameters

  • dockerfilePath: default Dockerfile.
  • contextPath: default directory containing the Dockerfile.
  • image: optional image tag.
  • registry: optional push target.
  • scan: default true.
  • sbom: default true.
  • maxSeverity: default high.
  • push: default false.
  • format: summary, json, or sarif; default summary.

Workflow

  1. Parse the Dockerfile and inspect .dockerignore and build context.
  2. Check base-image support, multi-stage builds, secret leakage, user identity, ports, health checks, and reproducible dependency inputs.
  3. Build without pushing unless explicitly requested.
  4. Scan the resulting image with the configured scanner and generate an SBOM.
  5. Verify runtime user, exposed capabilities, and immutable digest.
  6. Push only after explicit confirmation and a passing policy gate.

Safety

  • Never place secrets in Dockerfiles, layers, arguments, or labels.
  • Never push latest as the only release identifier.
  • Default to no registry mutation.
  • Report scanner limitations and unavailable checks.

Output

Return image identity, Dockerfile findings, vulnerability counts, SBOM path, non-root and runtime checks, digest, push status, and blockers.

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