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.
npx skills add WrongStack/WrongStack --skill container-hardeninggit clone --depth 1 https://github.com/WrongStack/WrongStackWrote 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.
[](https://agentmods.dev/skills/wrongstack/wrongstack/container-hardening)<a href="https://agentmods.dev/skills/wrongstack/wrongstack/container-hardening"><img src="https://agentmods.dev/badge/skills/wrongstack/wrongstack/container-hardening/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.
<a href="https://agentmods.dev/skills/wrongstack/wrongstack/container-hardening"><img src="https://agentmods.dev/badge/skills/wrongstack/wrongstack/container-hardening.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00045 | $0.00591 |
| Opus 5.5 | $0.00018 | $0.00236 |
| Sonnet 5.5 | $0.00009 | $0.00118 |
| Haiku 4.5 | $0.00005 | $0.00059 |
Grade A, and why
container-hardening 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Container Hardening
Selection card
- Task: Reduce container privilege and secret exposure.
- Start: Identify the authorized target, current health and rollback boundary.
- Finish: apply the acceptance checks below; report observed results and unresolved constraints.
Overview
Review and improve container image/runtime protection for an owned application with tested compatibility.
Use current Docker/OCI/runtime documentation and the deployed platform version. Checked Docker target: 29.9.0; apply settings supported by the actual runtime.
Rules
- Map the application required capabilities, files, network access and persisted data before restricting it.
- Use non-root execution, narrow writable paths and read-only filesystems where compatible.
- Avoid privileged mode, unnecessary host mounts and daemon-socket access; document any real requirement.
- Keep build/runtime credentials out of layers and logs; use supported secret mechanisms.
- Bound memory/CPU/processes according to measured needs and verify graceful degradation.
- Review image provenance/digests and advisory applicability; a scanner count alone does not determine release risk.
Workflow
- Inspect image/config and the actual exposure/ownership boundary.
- Record current privileges and source-supported risks.
- Apply a coherent narrow restriction set and rebuild/run the application.
- Exercise startup, persistence, shutdown and necessary network/device operations.
- Report implemented protections, compatibility checks and remaining justified privileges.
Before returning
Privilege requirements explicit; secrets excluded; protected configuration tested; findings and optional improvements distinguished.
Sources
Versioned facts checked 2026-10-09; refresh authoritative sources before new installs/upgrades. Docker security, Build secrets.
Skills in scope
- security-scanner — review owned source, configuration and dependency metadata for supported security findings with precise evidence and remediation.
- docker-deploy — docker deploy contracts and verification.
- compose-operations — operate and evolve multi-service Docker Compose environments with explicit networks, volumes and environment boundaries.
- kubernetes-operations — operate and deploy owned Kubernetes workloads with explicit cluster, namespace and rollout identity.
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.
- 7d ago Changed 30bcad4d86ae
- 8d ago First seen · 59 lines · 45 tokens per session scan A cccd1645a5f1
container-hardening is a skill published in the GitHub repository WrongStack/WrongStack (380 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 591 once invoked, about $0.0002 per session on Opus 5.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-10-10.
Other skills, from other repositories
infra-ci-cd-docker
Docker containerization patterns for Node.js/TypeScript development and production.
infra-containers-kubernetes
Kubernetes manifests, Helm charts, Kustomize overlays, and resource patterns.
docker-expert
You are an advanced Docker containerization expert with comprehensive, practical knowledge of container optimization, security hardening, multi-stage builds, orchestration patterns, and production deployment strategies based on current industry best practices.
agents-v2-py
Build container-based Foundry Agents with Azure AI Projects SDK (ImageBasedHostedAgentDefinition). Use when creating hosted agents with custom container images in Azure AI Foundry.
local-env-orchestration
Orchestrates local Kubernetes development environment management.
research-repository
Build a repository that makes findings findable, reusable, and cumulative across teams. Use when the same research keeps getting redone. For synthesising one study, use affinity-diagram.