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-podman-operationsgit 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-podman-operations)<a href="https://agentmods.dev/skills/knuckles-team/container-manager-mcp/container-manager-podman-operations"><img src="https://agentmods.dev/badge/skills/knuckles-team/container-manager-mcp/container-manager-podman-operations/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/knuckles-team/container-manager-mcp/container-manager-podman-operations"><img src="https://agentmods.dev/badge/skills/knuckles-team/container-manager-mcp/container-manager-podman-operations.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.00114 | $0.01823 |
| Opus 5 | $0.00057 | $0.00911 |
| Sonnet 5 | $0.00023 | $0.00365 |
| Haiku 4.5 | $0.00011 | $0.00182 |
Grade A, and why
container-manager-podman-operations scanned grade A 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
cm_podman action=podman_health_check container_id=<id> config={"test":["CMD","curl","-f","http://localhost/"]} How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Podman Pod/Kube Operations
Domain-typed control of Podman pods and Podman-specific features through
the single cm_podman tool on the container-manager-mcp server. Podman
groups containers into local pods (its rootless analogue of a Kubernetes pod) and
adds checkpoint/restore and Kubernetes-YAML interop that plain Docker doesn't have.
Prefer this cm_* tool over raw podman shell.
When to use
- Create/list/inspect/stop/remove a Podman pod, and read pod-scoped stats, top, or logs.
- Generate a Kubernetes YAML manifest from a running pod (
podman_generate_kube_yaml) or play a YAML manifest into local pods (podman_play_kube_yaml) — useful for Kubernetes-migration dry runs on a single host before targeting a real cluster. - Checkpoint a running container to disk and restore it later (live-migration / fast-restart workflows unique to Podman's CRIU integration).
- Manage pod-scoped networks and volumes, run a container health check, or prune the Podman system.
When NOT to use
- Single-container list/logs/stop/remove/exec, or plain images/compose →
container-manager-lifecycle(works for Podman too — it auto-detects the engine). - A real Kubernetes cluster (not just YAML interop) →
container-manager-kubernetes-operations. - Docker Swarm →
container-manager-swarm. - Operating Podman alongside other backends/contexts at once →
container-manager-multi-context.
Prerequisites & environment
Connect via the mcp-client skill against the container-manager-mcp MCP server.
A reachable Podman engine is required (rootless or rootful).
| Variable | Required | Notes |
|---|---|---|
CONTAINER_MANAGER_TYPE |
optional | Set to podman to force Podman (else auto-detect) |
PODMANTOOL |
optional | Tool toggle, default true; set false to hide cm_podman |
Tools & actions
| Tool | Group | Actions |
|---|---|---|
cm_podman |
Kubernetes interop | podman_generate_kube_yaml, podman_play_kube_yaml |
cm_podman |
Checkpoint/restore | podman_checkpoint, podman_restore |
cm_podman |
Pod management | podman_pod_create, podman_pod_list, podman_pod_stats, podman_pod_top, podman_pod_inspect, podman_pod_logs, podman_pod_stop, podman_pod_rm |
cm_podman |
Network | podman_network_create, podman_network_list, podman_network_inspect |
cm_podman |
Volume | podman_volume_create, podman_volume_list, podman_volume_inspect |
cm_podman |
System | podman_system_prune, podman_health_check |
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.
- 10d ago First seen · 142 lines · 114 tokens per session scan A 7444e177ebcb
container-manager-podman-operations is a skill published in the GitHub repository Knuckles-Team/container-manager-mcp (5 stars, last pushed 12d ago), licensed MIT. It adds 114 tokens to every session and 1,823 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
hardening-docker-daemon-configuration
Harden the Docker daemon by configuring daemon.json with user namespace remapping, TLS authentication, rootless mode, and CIS benchmark controls.
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…