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 medy-gribkov/arcana --skill container-securitygit clone --depth 1 https://github.com/medy-gribkov/arcanaWrote 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/medy-gribkov/arcana/container-security)<a href="https://agentmods.dev/skills/medy-gribkov/arcana/container-security"><img src="https://agentmods.dev/badge/skills/medy-gribkov/arcana/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.
<a href="https://agentmods.dev/skills/medy-gribkov/arcana/container-security"><img src="https://agentmods.dev/badge/skills/medy-gribkov/arcana/container-security.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.00037 | $0.01124 |
| Opus 5 | $0.00018 | $0.00562 |
| Sonnet 5 | $0.00007 | $0.00225 |
| Haiku 4.5 | $0.00004 | $0.00112 |
Grade A, and why
container-security 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 8d 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Image Scanning
Run Trivy before every push. Fail CI on HIGH or CRITICAL vulnerabilities.
trivy image myapp:latest --severity HIGH,CRITICAL --exit-code 1
Use Grype as a second scanner. Different scanners catch different CVEs.
grype myapp:latest --fail-on high
Store scan results as build artifacts for trending.
trivy image myapp:latest --format json --output scan-results.json
Minimal Base Images
Use distroless or scratch for runtime. Multi-stage builds separate build tools from runtime. See references/dockerfile-hardening.md for complete BAD/GOOD Dockerfile patterns for Go, Node.js, and static binaries.
Rootless Containers
Always create a non-root user and switch to it. For distroless, use the built-in nonroot user (UID 65532). See references/dockerfile-hardening.md for rootless patterns.
Secrets Management
BAD: Baking secrets into the image. They persist in layers even if deleted.
FROM node:24-alpine
ENV DATABASE_PASSWORD=supersecret
COPY . /app
CMD ["node", "server.js"]
GOOD: Inject secrets at runtime via environment variables or mounted files.
docker run -e DATABASE_PASSWORD="$(cat /secure/db-password)" myapp:latest
For Kubernetes, use Secrets mounted as volumes or environment variables.
env:
- name: DATABASE_PASSWORD
valueFrom:
secretKeyRef:
name: db-credentials
key: password
Build-Time Secrets
Use BuildKit secrets for credentials needed during build (e.g., private registry tokens).
BAD: Copying .env file into the image.
COPY .env /build/.env
RUN npm install --registry=https://private.npm.com
GOOD: Mount secrets during build without persisting them.
# syntax=docker/dockerfile:1
RUN --mount=type=secret,id=npmrc,target=/root/.npmrc \
npm install --registry=https://private.npm.com
Build with:
docker buildx build --secret id=npmrc,src=.npmrc .
Audit .dockerignore
What ships with it
2 files 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.
- 8d ago First seen · 206 lines · 37 tokens per session scan A 0640b515acef
container-security is a skill published in the GitHub repository medy-gribkov/arcana (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 1,124 once invoked, about $0.0002 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-31.
Other skills, from other repositories
compose-creator
Create docker-compose configurations — service definitions, networks, volumes, health checks, and environment management.
docker-composer
Write Dockerfiles and docker-compose files — multi-stage builds, health checks, volumes, networks, and production configurations.
helm-chart-builder
Create Helm charts — templates, values, helpers, hooks, tests, and OCI chart publishing.
kubernetes-helper
Author Kubernetes manifests — Deployments, Services, Ingress, ConfigMaps, Secrets, HPA, and Helm charts.
dockerfile-builder
Write optimized Dockerfiles — multi-stage builds, layer caching, security hardening, and minimal image sizes.
docker-devops
Docker/K8s: Dockerfile, multi-stage, compose, manifests, Helm. Triggers: Docker, Dockerfile, container, Kubernetes, k8s, compose, Helm, pod.