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-config-walkthroughgit 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-config-walkthrough)<a href="https://agentmods.dev/skills/knuckles-team/container-manager-mcp/container-manager-config-walkthrough"><img src="https://agentmods.dev/badge/skills/knuckles-team/container-manager-mcp/container-manager-config-walkthrough/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-config-walkthrough"><img src="https://agentmods.dev/badge/skills/knuckles-team/container-manager-mcp/container-manager-config-walkthrough.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.00119 | $0.02622 |
| Opus 5 | $0.00060 | $0.01311 |
| Sonnet 5 | $0.00024 | $0.00524 |
| Haiku 4.5 | $0.00012 | $0.00262 |
Grade A, and why
container-manager-config-walkthrough 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 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.
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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Container Manager — Configuration Walkthrough
The one-time (or per-environment) setup path for container-manager-mcp before
using any of its operational skills. This skill is a checklist and decision guide,
not an operations surface — it drives only the read-only discovery/diagnostic tools
(cm_doctor, cm_info_operations, cm_list_hosts,
cm_k8s_cluster action=list_contexts) needed to confirm the environment is wired
correctly.
Step 1 — run the doctor first (diagnose + get remediation)
Before anything else, run the guided environment doctor — it probes every surface (backends, config/env, inventory, docker, podman, kubernetes) with real checks and prints concrete remediation for each non-OK result, so you are walked through connecting to your environments instead of guessing.
CLI:
container-manager-doctor # diagnose everything (exit 1 if any FAIL)
container-manager-doctor --guided # + probe every inventory host, verbose remediation
container-manager-doctor --backend kubernetes --context prod
container-manager-doctor --backend inventory --host <alias>
container-manager-doctor --backend docker --host <alias>
container-manager-doctor --json # machine-readable report
MCP tool (same engine):
cm_doctor action=run # full sweep
cm_doctor action=check_backends # python libs + CLIs + config/env
cm_doctor action=check_inventory host=<alias> # inventory file + SSH reachability
cm_doctor action=check_docker host=<alias> # docker daemon (local or over-SSH)
cm_doctor action=check_podman # podman service socket
cm_doctor action=check_kubernetes context=<ctx> # kubeconfig + per-context probe
Each check returns {name, category, status: ok|warn|fail, detail, remediation}.
Fix (or hand off) every fail, then continue with the decision guide below.
When to use
- Standing up container-manager-mcp against a new environment for the first time.
- Deciding which backend (
docker/podman/kubernetes/multi) an agent should target before picking an operational skill. - Troubleshooting "no hosts found" / "no contexts found" / wrong-engine errors.
- Onboarding a remote Docker/Podman host or a remote Kubernetes cluster and need the split between the two connection models spelled out.
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 · 193 lines · 119 tokens per session scan A 8a28d4140418
container-manager-config-walkthrough is a skill published in the GitHub repository Knuckles-Team/container-manager-mcp (5 stars, last pushed 12d ago), licensed MIT. It adds 119 tokens to every session and 2,622 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.
hsb-setup
Clone the latest NVIDIA Holoscan Sensor Bridge repo, ask which supported devkit is being used, configure the host per platform, build the correct demo container, run it, and verify HSB connectivity by pinging 192.168.0.2. Use for Holoscan Sensor Bridge setup, build, container launch, and first-connectivity bring-up.
tao-setup-nvidia-gpu-host
Host setup for TAO GPU backends. Checks and, after user approval, installs minimum-compatible NVIDIA driver, CUDA Toolkit, and NVIDIA Container Toolkit versions for Docker/local-Docker and Kubernetes GPU worker hosts. TAO-wide defaults can be overridden by the selected model's runtime profile. The --check-only path…
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…