Individual skill

container-security

Secure containerized workloads — image hardening, registry scanning, runtime protection, and supply-chain integrity.

skills/container-security/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
54
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Overview

Containers package applications with their dependencies — which means they also package vulnerabilities, misconfigurations, and secrets at scale and speed. Container security covers the full lifecycle: hardened base images, scanned registries, signed artifacts, least-privilege runtime, and monitoring for anomalous container behavior.

This skill gives you the defensive lifecycle: build secure images, verify what you deploy, constrain what runs, and watch it in production.

Shift left with guardrails, not gates: image scanning and policy checks in the pipeline should guide developers with fast feedback, not become a security tollbooth that everyone routes around. The goal is secure-by-default base images and pipelines, so the average developer never has to think about it.

## When to use

- Building the container security program (image standards, registry, runtime).
- Remediating scanner findings: vulnerable base images, misconfigurations, leaked secrets.
- Defining admission policies (what may deploy to the cluster).
- Responding to a compromised container or malicious image.