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 jeremylongworth-source/AgentSkills --skill containerization-plangit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/jeremylongworth-source/agentskills/containerization-plan)<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/containerization-plan"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/containerization-plan/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/jeremylongworth-source/agentskills/containerization-plan"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/containerization-plan.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.00054 | $0.00319 |
| Opus 5.5 | $0.00022 | $0.00128 |
| Sonnet 5.5 | $0.00011 | $0.00064 |
| Haiku 4.5 | $0.00005 | $0.00032 |
Grade A, and why
containerization-plan 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.
What it actually says
Containerization Plan
Core Workflow
- Identify app runtime, build process, target environment, ports, volumes, secrets, healthchecks, and deployment constraints.
- Choose image strategy: base image, multi-stage build, dependency caching, non-root user, filesystem layout, and startup command.
- Define runtime config: env vars, secrets, volumes, network, healthcheck, resource limits, and logs.
- Review size, reproducibility, security, and local development needs.
- Include build, run, smoke test, and publish steps.
- Flag risks before creating production images.
Safety Rules
- Do not bake secrets, tokens, private keys, or local paths into images.
- Do not run containers as root by default when a non-root runtime is practical.
- Do not publish images or push registries without explicit approval.
Deliverable Shape
For containerization plans, provide:
- Runtime and target environment
- Image build strategy
- Runtime configuration
- Security and secret handling
- Healthcheck and logging
- Build/run/test commands
- Registry and release notes
- Open risks
References
- Read
references/containerization-plan-checklist.mdwhen planning or reviewing container setup.
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 · 44 lines · 54 tokens per session scan A 8efbd18474bb
containerization-plan is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 17d ago), licensed MIT. It adds 54 tokens to every session and 319 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-09-03.
Other skills, from other repositories
authos-platform-deployment
Deploy and configure an AuthOS API instance from source or Docker. Use when setting database backend, JWT signing keys, environment variables, billing provider, SMTP, GeoIP, Docker images, health checks, or production reverse proxy settings.
dynamo-recipe-runner
Select, validate, patch, and deploy existing NVIDIA Dynamo Kubernetes recipes. Use for model/backend/GPU/deployment-mode recipe bring-up; use router-starter for router-only mode work and troubleshoot for broken deployments.
kermt-monitor
Check progress for a detached KERMT run (pretrain, finetune, or any kermtrundetached invocation). Reads run.json, queries docker for container state, tails the pretrain/finetune log, and parses progress lines (epoch, step, val loss).
holoscan-install-source
Build and verify Holoscan SDK 5.x from an explicit source ref with the repository run wrapper; use for Early Access or SDK development.
doca-argus
Use this skill when the user is deploying or operating the DOCA Argus Service — the packaged BlueField-side runtime-security container that watches the BlueField and attached host for suspicious activity, integrity violations, and operational anomalies, and forwards findings to a SIEM (Splunk / ELK / Sentinel /…
routeros-container
RouterOS /container subsystem for running OCI containers on MikroTik devices. Use when: enabling containers on RouterOS, setting up VETH/bridge networking for containers, managing container lifecycle via CLI or REST API, building OCI images for RouterOS, configuring container environment variables, troubleshooting…