auditing-container-image-provenance SKILL.md skillA
auditing-container-image-provenance from unboundcompute/security-agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add unboundcompute/security-agent-skills/auditing-container-image-provenance@git:20260828.ce55026Pins git:20260828.ce55026 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- unboundcompute/security-agent-skills
- Path
skills/auditing-container-image-provenance/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260828.ce55026, committed Aug 28, 2026
- Size
- 9,076 bytes
- Repository stars
- 26
- License
- MIT
Audit how a cluster decides which container images to trust and run: an image referenced by a mutable tag rather than a content digest, a workload pulling from a registry that admits unsigned or unverified images, a signature or attestation policy that is configured but not enforced at admission, and a base image or layer whose origin the pipeline never verified. Covers Kubernetes and container platforms where the image a workload runs is the code that runs, and where tag mutability, signing…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Auditing container image provenance: when the tag is not the artifact The image a workload runs is the code it runs, and a container reference is only a promise about which bytes those are. A mutable tag can point at different content over time, so a workload pinned to a tag runs whatever that tag resolves to at pull time, not the artifact that was reviewed. Signing and provenance attestation exist to close that gap, but only if they are enforced at admission rather than merely produced in the pipeline: a signature nobody verifies is decoration, and an attestation the cluster does not require proves nothing to the cluster. The failure is quiet because the workload starts and runs; the question is whether what it runs is provably the artifact you intended. You audit this by tracing each workload's image reference back to a verified digest and confirming the cluster refuses anything unproven. ## When to use - Workloads reference images by mutable tags rather than immutable content digests. - Image signing or provenance attestation is produced but may not be enforced at admission. - Images are pulled from registries or base images whose origin the pipeline does not verify. …
Read the whole file at its exact version.
How to install
mdr add unboundcompute/security-agent-skills/auditing-container-image-provenance@sha256:ac7773da97964bd0The line at the top of this page pins the label git:20260828.ce55026, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_7tdtjgw6lu7ekcyt)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 28, 2026.
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 (9076 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
unboundcompute/security-agent-skills · 26 stars · license MIT · pushed 2026-09-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7tdtjgw6lu7ekcyt GET https://markdownregistry.com/api/v1/resolve?ref=unboundcompute/security-agent-skills/auditing-container-image-provenance GET https://markdownregistry.com/api/v1/blob/ac7773da97964bd0b6942c5b475acafb7012627edbd1378c9d143d8047997efb
Your AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.