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 Knuckles-Team/container-manager-mcp --skill container-manager-lifecyclegit clone --depth 1 https://github.com/Knuckles-Team/container-manager-mcpWrote 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/knuckles-team/container-manager-mcp/container-manager-lifecycle)<a href="https://agentmods.dev/skills/knuckles-team/container-manager-mcp/container-manager-lifecycle"><img src="https://agentmods.dev/badge/skills/knuckles-team/container-manager-mcp/container-manager-lifecycle.svg" alt="Measured on agentmods" 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.00111 | $0.01264 |
| Opus 5 | $0.00056 | $0.00632 |
| Sonnet 5 | $0.00022 | $0.00253 |
| Haiku 4.5 | $0.00011 | $0.00126 |
Grade A, and why
container-manager-lifecycle 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 6d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Container Lifecycle (Docker / Podman)
Domain-typed control of single-host container workloads through the
container-manager-mcp server. Prefer these cm_* tools over raw docker/podman
shell — they carry the host-targeting, port-tracing, and destructive-confirmation
conventions and return typed records.
When to use
- List, inspect, or read logs from containers on the LOCAL socket or a remote host.
- Stop / remove / prune containers, or
execa command inside one. - Find which container is publishing a given host port.
- Pull, list, or prune images; bring a
docker-composefile up/down.
When NOT to use
- Swarm cluster services, replicas, or nodes →
container-manager-swarm. - Snapshotting inventory into the knowledge graph →
container-manager-kg-ingestion. - Kubernetes workloads →
container-manager-kubernetes-operations(the fullcm_k8s_*surface), not these tools. - Podman pods, checkpoint/restore, or Kubernetes-YAML interop →
container-manager-podman-operations.
Prerequisites & environment
Connect via the mcp-client skill against the container-manager-mcp MCP server.
A reachable Docker/Podman engine is required (local socket or a remote host over SSH).
| Variable | Required | Notes |
|---|---|---|
CONTAINER_MANAGER_TYPE |
optional | docker or podman; auto-detected if unset |
CONTAINER_MANAGER_HOST |
optional | Default remote host alias (else LOCAL socket) |
Remote hosts resolve from the tunnel-manager inventory — call cm_list_hosts to see
aliases. Omit host to target the LOCAL Docker socket. MCP_TOOL_MODE
(condensed|verbose|both) selects the condensed action-based tools (used below).
Tools & actions
| Condensed tool | Actions |
|---|---|
cm_container_operations |
list_containers, get_container_logs, stop_container, remove_container, prune_containers, exec_in_container |
cm_image_operations |
list_images, pull_image, remove_image, prune_images |
cm_compose_operations |
up, down, ps, logs |
trace_port_namespace |
(single-purpose) locate the container owning a host port |
cm_list_hosts |
enumerate remote host aliases |
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.
- 6d ago First seen · 108 lines · 111 tokens per session scan A 7c67cc1ce9d6
container-manager-lifecycle is a skill published in the GitHub repository Knuckles-Team/container-manager-mcp (5 stars, last pushed 9d ago), licensed MIT. It adds 111 tokens to every session and 1,264 once invoked, about $0.0006 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
docker
Use when authoring or auditing a Dockerfile, shrinking a bloated image, hardening a container that runs as root, picking a base image, or wiring a Compose dev loop with hot reload. NOT CI builds or deploy-to-host (that is deployment), NOT k8s autoscaling (that is scaling), NOT app-level injection or secrets-in-code…
docker-compose-generator
Generate Docker Compose configurations for development environments - auto-detect project stack, configure services with dependencies, volumes, networking, and health checks.
buildah
Buildah OCI container image builder reference. Build container images without Docker daemon. Covers Containerfile builds, scripted builds with shell commands, direct filesystem mount, rootless operation, multi-arch manifests, and CI/CD integration.
deployment
Use when taking an app from source to live: choosing the deploy target from requirements (Hetzner+Coolify vs Vercel vs a third), then wiring container → CI → registry → host with build secrets, healthchecks and rollback. NOT one platform's mechanics (that is coolify, vercel, railway, render), NOT the Dockerfile alone…
coolify
Use when self-hosting apps and databases with Coolify on a VPS you own — install, first-admin lockdown, Git-to-deploy (Nixpacks/Dockerfile/compose), managed Postgres/Redis, scheduled S3 backups, domains + auto-SSL. NOT a PaaS someone else runs (that is railway), NOT sizing/hardening the box (that is hetzner), NOT…
performing-container-image-hardening
This skill covers hardening container images by minimizing attack surface, removing unnecessary packages, implementing multi-stage builds, configuring non-root users, and applying CIS Docker Benchmark recommendations to produce secure production-ready images.