agentmods.dev

container-remediation

container-remediation is a skill for Claude Code, Codex from tahirraufkeeyu/software-development-agent-stack--sdas. It costs 80 tokens per session (3,699 once invoked), scanned A, original, MIT.

A workflow for rebuilding a Docker or OCI container image after a security scanner finds serious vulnerabilities. It updates the base image and packages, improves the Dockerfile, removes exposed secrets, and checks that findings are closed.

In plain words
What is it for?
Use it after a container scan reports high- or critical-severity findings, an outdated base image, root execution, missing health checks, or secrets stored in image layers.
Why use it?
It turns scanner results into a tracked remediation process and helps produce a safer replacement image for deployment.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is COPY src/ ./src/.

not rated 18repo 4mo ago A scan 80 tokens original MIT

Good fit Use it after a container scan reports high- or critical-severity findings, an outdated base image, root execution, missing health checks, or secrets stored in image layers.

Compare 6 skills from other repositories ↓
View source ↗ tahirraufkeeyu/software-development-agent-stack--sdas
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/tahirraufkeeyu/software-development-agent-stack--sdas
agentmods
npx agentmods add skills/tahirraufkeeyu/software-development-agent-stack--sdas/container-remediation

Made for: Claude Code, Codex.

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-remediation

README.md
[![agentmods](https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/container-remediation/github.svg)](https://agentmods.dev/skills/tahirraufkeeyu/software-development-agent-stack--sdas/container-remediation)
Your own site
<a href="https://agentmods.dev/skills/tahirraufkeeyu/software-development-agent-stack--sdas/container-remediation"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/container-remediation/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-remediation

Your own site · 80×15
<a href="https://agentmods.dev/skills/tahirraufkeeyu/software-development-agent-stack--sdas/container-remediation"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/container-remediation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,699 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00080 $0.03699
Opus 5 $0.00040 $0.01850
Sonnet 5 $0.00016 $0.00740
Haiku 4.5 $0.00008 $0.00370

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

Security

Grade A, and why

container-remediation scanned grade A with 0 findings 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 10d 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

departments/security/skills/container-remediation/SKILL.md · 328 lines

How it starts

The opening of the file, as written. The whole thing — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.

When to use

  • container-scan has produced security/findings/container.json with HIGH or CRITICAL findings.
  • A registry vulnerability scanner (ECR, GCR, Harbor, Docker Hub) has flagged an image and blocked promotion.
  • A base-image update is available that closes multiple open CVEs in one rebase.
  • The image is running as root, has a shell as PID 1, or is missing standard Dockerfile hygiene and you're doing a posture pass.
  • An audit discovered a secret baked into a layer (visible via docker history or dive).

Do not use this skill to fix application-code vulnerabilities inside the image — that's vulnerability-remediation. Do not use it to fix runtime K8s misconfig (PodSecurityStandard, seccomp) — that's an infrastructure skill.

Inputs

  • security/findings/container.json with image name, tag, digest, and findings list.
  • The Dockerfile (and any multi-stage chain) that produced the image.
  • Registry push credentials and a CI build runner.
  • The downstream deployment manifests (K8s, ECS, Nomad) so the new digest can be rolled out.

Outputs

  • security/remediation/container-<image>-<date>.md — remediation audit trail.
  • A new image tag pushed to the registry, pinned by digest in deployment manifests.
  • A hardened, smaller, reproducibly-built Dockerfile.
  • Trivy re-scan output attached to the report.

Tool dependencies

  • docker (or podman, buildah) with BuildKit enabled (DOCKER_BUILDKIT=1).
  • trivy for image + secret + misconfig scanning.
  • dive or docker history for layer inspection.
  • cosign for image signing (optional but recommended).
  • Registry CLI: aws ecr, gcloud, docker login, as applicable.

Procedure

  1. Classify findings. Each entry in container.json falls into one of:

    Bucket Source Fix approach
    OS-package CVE apt/apk/yum package in base Rebase to patched base tag; rebuild
    Language runtime CVE e.g. Node/Python binary shipped in base Rebase to patched runtime tag
    Dockerfile misconfig USER root, shell PID 1, no HEALTHCHECK, COPY .env Rewrite Dockerfile
    Secret in layer docker history shows env-var or COPY'd file Rebuild from scratch using BuildKit --mount=type=secret; also rotate (hand off to secret-remediation)
    Large attack surface Bloated image with dev tools at runtime Multi-stage split, drop tool chain from runner

Read the full file on GitHub · 328 lines

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. 10d ago First seen · 328 lines · 80 tokens per session scan A e049a985b30d

Subscribe to this mod's changes

container-remediation is a skill published in the GitHub repository tahirraufkeeyu/software-development-agent-stack--sdas (18 stars, last pushed 4mo ago), licensed MIT. It adds 80 tokens to every session and 3,699 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

ContainersDevOps and cloudSecurity
Related

Other skills, from other repositories

deploy-docker-compose

Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…

omnigent-ai/omnigent · 84 tokens

compute-env-setup

Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.

companion-inc/feynman · 45 tokens

securing-kubernetes-on-cloud

This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…

xalgorix/xalgorix · 80 tokens

detecting-privilege-escalation-in-kubernetes-pods

Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.

xalgorix/xalgorix · 40 tokens

implementing-rbac-hardening-for-kubernetes

Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.

xalgorix/xalgorix · 41 tokens

docker-socket-mount

Docker / containerd socket mounted into a container → host RCE. Common in CI runners, GitOps controllers (ArgoCD, Flux), and 'Docker-in-Docker' setups. Single-command escape via docker run --rm --privileged -v /:/host alpine chroot /host.

PurpleAILAB/Decepticon · 67 tokens