container-security

container-security is a skill for Kiro from ihatesea69/kiro-kit. It costs 25 tokens per session (275 once invoked), scanned A, original, MIT.

A set of practices for securing container images and the environments where containers run. Containers package an application with its dependencies so it can run consistently across systems.

In plain words
What is it for?
Use it to harden Dockerfiles, scan images, sign and verify images, and configure safer Kubernetes or container runtime settings.
Why use it?
It helps reduce vulnerabilities, limit what a container can do, and prevent secrets or unsafe settings from reaching production.

Skill for Kiro

Written for Kiro: installed under .kiro/.

Good fit Use it to harden Dockerfiles, scan images, sign and verify images, and configure safer Kubernetes or container runtime settings.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ihatesea69/kiro-kit/container-security
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add ihatesea69/kiro-kit --skill container-security
Clone the repo
git clone --depth 1 https://github.com/ihatesea69/kiro-kit

Made for: Kiro.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for container-security

README.md
[![agentmods](https://agentmods.dev/badge/skills/ihatesea69/kiro-kit/container-security/github.svg)](https://agentmods.dev/skills/ihatesea69/kiro-kit/container-security)
Your own site
<a href="https://agentmods.dev/skills/ihatesea69/kiro-kit/container-security"><img src="https://agentmods.dev/badge/skills/ihatesea69/kiro-kit/container-security/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for container-security

Your own site · 80×15
<a href="https://agentmods.dev/skills/ihatesea69/kiro-kit/container-security"><img src="https://agentmods.dev/badge/skills/ihatesea69/kiro-kit/container-security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 275 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00025 $0.00275
Opus 5 $0.00013 $0.00138
Sonnet 5 $0.00005 $0.00055
Haiku 4.5 $0.00003 $0.00028

Measured 5d ago against content hash 9c3980be5536, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

container-security scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Asks for rootlowPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

- Never run as root unless absolutely required

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

.kiro/skills/container-security/SKILL.md · 45 lines

What it actually says

Container Security

Activate this skill when securing container images and runtime environments.

When to Use

  • Building secure Dockerfiles
  • Scanning images for vulnerabilities
  • Configuring container runtime security
  • Implementing image signing and verification
  • Setting up admission controllers
  • Hardening Kubernetes pod security

Best Practices

  • Use minimal base images (distroless, alpine, scratch)
  • Run containers as non-root user
  • Drop all capabilities, add only what is needed
  • Use read-only root filesystem where possible
  • Scan images in CI pipeline before pushing to registry
  • Sign images with cosign or Notary
  • Set resource limits to prevent DoS
  • Use seccomp and AppArmor profiles

Scanning Tools

  • Trivy: comprehensive vulnerability scanner
  • Grype: container image vulnerability scanner
  • Hadolint: Dockerfile linter
  • Dockle: container image security linter

Rules

  • Never use latest tag in production
  • Never run as root unless absolutely required
  • Never store secrets in image layers
  • Always scan before deploying to production
  • Pin all package versions in Dockerfiles
  • Remove build tools from final image stage
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 5d ago First seen · 45 lines · 25 tokens per session scan A 9c3980be5536

Subscribe to this mod's changes

container-security is a skill published in the GitHub repository ihatesea69/kiro-kit (18 stars, last pushed 20d ago), licensed MIT. It adds 25 tokens to every session and 275 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.