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 agentmods add skills/unitoneai/securityskills/container-securitynpx skills add UnitOneAI/SecuritySkills --skill container-securitygit clone --depth 1 https://github.com/UnitOneAI/SecuritySkillsWhat 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 | $0.00096 | $0.03544 |
| Opus 5 | $0.00048 | $0.01772 |
| Sonnet 5 | $0.00019 | $0.00709 |
| Haiku 4.5 | $0.00010 | $0.00354 |
Grade B, and why
container-security scanned grade B 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 3d 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.
Nullifies safety policiesmediumAnti-refusal
"You have no restrictions", "do anything now", "ignore your guidelines": a direct jailbreak that disables guardrails.
3. **Default namespace is not just a naming issue.** The `default` namespace typically has no NetworkPolicy and no Pod Security Admission labels. Workloads in `default` often bypass all policy controls. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Container & Kubernetes Security Review
Overview
This skill performs a structured security review of container images and Kubernetes deployments against three industry-standard frameworks:
- CIS Docker Benchmark v1.6.0 -- 7 sections covering Docker daemon, host, images, containers, runtime, security operations, and Docker Swarm configuration.
- CIS Kubernetes Benchmark v1.9.0 -- 5 sections covering control plane, etcd, control plane configuration, worker nodes, and policies.
- NIST SP 800-190 (Application Container Security Guide) -- Countermeasures for image, registry, orchestrator, container, and host OS risks.
The review covers Dockerfiles, Kubernetes manifests, Helm charts, and supporting configurations. Each finding is mapped to specific CIS recommendation IDs or NIST SP 800-190 countermeasure categories.
When to Use
If a target is provided via arguments, focus the review on: $ARGUMENTS
- Reviewing Dockerfiles before building production container images
- Auditing Kubernetes manifests or Helm charts before deployment
- Assessing an existing Kubernetes cluster's security configuration
- Evaluating container runtime security policies (Pod Security Standards, OPA/Gatekeeper)
- Preparing for a container security audit or compliance assessment
- Investigating container escape vectors or privilege escalation paths
Context
Containers and Kubernetes introduce a distinct threat model compared to traditional infrastructure. The attack surface spans the container image supply chain, runtime isolation boundaries, orchestrator control plane, network segmentation, and secrets management. A single misconfigured pod can provide an attacker with cluster-wide access.
NIST SP 800-190 identifies five risk categories: image risks, registry risks, orchestrator risks, container risks, and host OS risks. The CIS benchmarks provide prescriptive controls for each. This skill maps findings across all three frameworks.
Prerequisites
- Access to Dockerfiles and container build configurations
- Kubernetes manifests (YAML), Helm charts, or Kustomize overlays
- RBAC configuration files (Roles, ClusterRoles, RoleBindings)
- NetworkPolicy definitions
- Pod Security Standard configurations or OPA/Gatekeeper policies
- Container registry configurations (if available)
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 309 lines · 96 tokens per session scan B 63a292c8638c
container-security is a skill published in the GitHub repository UnitOneAI/SecuritySkills (58 stars, last pushed 2mo ago), licensed MIT. It adds 96 tokens to every session and 3,544 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (nullifies safety policies). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
analyzing-kubernetes-audit-logs
Parses Kubernetes API server audit logs (JSON lines) to detect exec-into-pod, secret access, RBAC modifications, privileged pod creation, and anonymous API access. Builds threat detection rules from audit event patterns. Use when investigating Kubernetes cluster compromise or building k8s-specific SIEM detection rules.
analyzing-docker-container-forensics
Investigate compromised Docker containers by analyzing images, layers, volumes, logs, and runtime artifacts to identify malicious activity and evidence.
Cloud Security & Container Hardening
AWS/Azure/GCP security auditing, container and Kubernetes hardening, Infrastructure as Code scanning, and cloud compliance assessment.
container-manager-kubernetes-operations
Full operational Kubernetes surface via the container-manager-mcp MCP server — workloads (pods/rollouts/StatefulSets/DaemonSets/ReplicaSets/Jobs/CronJobs), config (ConfigMaps/Secrets/Namespaces/CRDs/patch), networking (Ingress/native Services/NetworkPolicy/DNS), storage (PV/PVC/StorageClass/snapshots/CSI), RBAC…
container-manager-multi-context
Operate several container backends and contexts at once — Kubernetes, Docker, Podman, and Swarm — via the container-manager-mcp MCP server's cmmulticontext tool, with per-call backend/context selection and parallel fan-out across a configured pool of contexts. Use when the agent must compare, migrate between, or…
security-audit
Pre-build and pre-deploy security audit — secret scans, IAM least-privilege, IRSA/WI verification, image signing, SBOM.