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.
git clone --depth 1 https://github.com/fmind/dotfilesnpx agentmods add skills/fmind/dotfiles/containerizeWrote 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/fmind/dotfiles/containerize)<a href="https://agentmods.dev/skills/fmind/dotfiles/containerize"><img src="https://agentmods.dev/badge/skills/fmind/dotfiles/containerize/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/fmind/dotfiles/containerize"><img src="https://agentmods.dev/badge/skills/fmind/dotfiles/containerize.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.00047 | $0.01424 |
| Opus 5.5 | $0.00019 | $0.00570 |
| Sonnet 5.5 | $0.00009 | $0.00285 |
| Haiku 4.5 | $0.00005 | $0.00142 |
Grade A, and why
containerize 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 1mo 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Containerize an Application
Build a small, non-root, reproducible OCI image and verify it before it ships. Pairs with k8s-local for the local dev loop and security-scan for image scanning.
Choose an Approach
-
Go →
ko(default, no Dockerfile): builds a minimal, shell-less, multi-arch, reproducible image straight from a package path (base defaults tocgr.dev/chainguard/static, override withKO_DEFAULTBASEIMAGE). Pin it per project (go get -tool github.com/google/ko, thengo tool ko) so builds stay reproducible even where a global toolchain already providesko.export KO_DOCKER_REPO=registry.localhost:5050/<slug> # or a real registry go tool ko build ./cmd/<slug> --bare --platform=linux/amd64,linux/arm64 -
Python (or any other language) → multi-stage Dockerfile on a distroless or minimal base (optimized with
uv). Copy and customize the image digests and the<slug>console-script entry point:# Build locally for current platform docker build -t <registry>/<slug>:<tag> . # Build multi-platform using Buildx (recommended for multi-arch registries) docker buildx build --platform linux/amd64,linux/arm64 -t <registry>/<slug>:<tag> --push .
Verify Before Ship
- Resolve the immutable digest emitted by the registry after the push. Use that digest for every scan, signature, SBOM, and deployment reference; never sign a mutable tag.
- Scan the built image (fail on HIGH/CRITICAL — see security-scan):
trivy --config trivy.yaml image <registry>/<slug>@<digest> - Sign and verify keyless with Sigstore (OIDC, no long-lived keys). Verification must bind the certificate to the expected workflow identity and OIDC issuer:
cosign sign --yes <registry>/<slug>@<digest> # --yes is mandatory: cosign prompts by default and hangs any CI job or agent session cosign verify \ --certificate-identity '<expected-certificate-identity>' \ --certificate-oidc-issuer '<expected-oidc-issuer>' \ <registry>/<slug>@<digest> - SBOM for a portable component inventory:
trivy --config trivy.yaml image --format cyclonedx -o sbom.json <registry>/<slug>@<digest>
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.
- 1mo ago First seen · 99 lines · 47 tokens per session scan A 93558da57b93
containerize is a skill published in the GitHub repository fmind/dotfiles (4 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 1,424 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-08-31.
Other skills, from other repositories
airflow
Develop and test Airflow DAGs with the Astronomer astro CLI.
docker
Run Docker, Compose, and Colima; build, scan, sign, and verify Python images.
kubernetes
Operate Kubernetes with kubectl, Helm, k9s, kustomize, and stern.
full-review
Full review: read every repo area, apply verified fixes, and prove all checks pass.
duckdb
Query and export CSV, Parquet, JSON, or SQLite data with DuckDB.
observability
Instrument Python services and agents: structlog logs, OpenTelemetry traces and metrics.