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 podman-mesh-provisionergit 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/podman-mesh-provisioner)<a href="https://agentmods.dev/skills/knuckles-team/container-manager-mcp/podman-mesh-provisioner"><img src="https://agentmods.dev/badge/skills/knuckles-team/container-manager-mcp/podman-mesh-provisioner/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/podman-mesh-provisioner"><img src="https://agentmods.dev/badge/skills/knuckles-team/container-manager-mcp/podman-mesh-provisioner.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.00110 | $0.01014 |
| Opus 5 | $0.00055 | $0.00507 |
| Sonnet 5 | $0.00022 | $0.00203 |
| Haiku 4.5 | $0.00011 | $0.00101 |
Grade B, and why
podman-mesh-provisioner scanned grade B 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 11d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Rootful: `sudo systemctl enable --now podman.socket` → `/run/podman/podman.sock`. How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Podman Mesh Provisioner Skill
Stateless atomic operation to stand up a Podman-based container runtime — rootful
or rootless — across one or more hosts, as a first-class peer to Docker Swarm and
Kubernetes. Podman has no built-in clustering daemon; the "mesh" is the API socket +
podman-compose locally and Podman system connections over SSH for remote hosts
(the same Docker-over-SSH inventory model container-manager-mcp already uses).
Prerequisites
container-manager-mcp— setCONTAINER_MANAGER_TYPE=podmanand (optionally)COMPOSE_TOOL=podman-compose; it drives Podman socket/compose/host operations.tunnel-manager-mcp— remote command execution + the shared~/.config/agent-utilities/inventory.yaml.
Inputs
rootless(bool, default true) — rootless runs the Podman socket under the invoking user ($XDG_RUNTIME_DIR/podman/podman.sock, no daemon, better isolation); rootful uses the system socket (/run/podman/podman.sock) for host-network / low ports / shared volumes.hosts— inventory aliases to provision (default: the controller only).
Steps
Step 1: Select the Podman mode (rootful vs rootless)
Resolve the rootless input. For rootless, ensure lingering is enabled so the
user socket survives logout (loginctl enable-linger <user>) and that subuid/subgid
ranges exist for the user. For rootful, operations run against the system socket
and require privileged access on the host.
Step 2: Enable the Podman API socket
Enable and start the Podman socket service so container-manager-mcp can speak the
Podman API:
- Rootless:
systemctl --user enable --now podman.socket→$XDG_RUNTIME_DIR/podman/podman.sock. - Rootful:
sudo systemctl enable --now podman.socket→/run/podman/podman.sock. Record the resolved socket path asCONTAINER_MANAGER_PODMAN_BASE_URL(unix://<socket>).
Step 3: Wire podman-compose
Confirm podman-compose (or podman compose) is available; set COMPOSE_TOOL=podman-compose
so stack deploys route through Podman rather than Docker.
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.
- 11d ago First seen · 90 lines · 110 tokens per session scan B 5fc18bda6bc0
podman-mesh-provisioner is a skill published in the GitHub repository Knuckles-Team/container-manager-mcp (5 stars, last pushed 13d ago), licensed MIT. It adds 110 tokens to every session and 1,014 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). 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…