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 kolodkin/devpowers --skill local-docker-debuggit clone --depth 1 https://github.com/kolodkin/devpowersWrote 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/kolodkin/devpowers/local-docker-debug)<a href="https://agentmods.dev/skills/kolodkin/devpowers/local-docker-debug"><img src="https://agentmods.dev/badge/skills/kolodkin/devpowers/local-docker-debug/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/kolodkin/devpowers/local-docker-debug"><img src="https://agentmods.dev/badge/skills/kolodkin/devpowers/local-docker-debug.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.00068 | $0.00986 |
| Opus 5.5 | $0.00027 | $0.00394 |
| Sonnet 5.5 | $0.00014 | $0.00197 |
| Haiku 4.5 | $0.00007 | $0.00099 |
Grade A, and why
local-docker-debug 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `curl` for connectivity checks against services the user explicitly asks about How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Local Docker Debugging
Discover and tail logs for Docker containers running on the local Docker daemon.
Arguments
/local-docker-debug [container-name ...]
- container-name (optional, repeatable) — One or more container names or IDs to tail. If omitted, run the discovery phase and ask the user which containers to tail.
IMPORTANT
This skill is strictly read-only on the local Docker daemon. NEVER run docker exec, docker build, docker compose up/down, docker run, docker rm, docker stop, docker restart, or any command that modifies container or host state. Only the following are allowed:
docker ps(and variants with--format,-a,--filter)docker logs(with--tail,--since,-f)docker inspect(read-only metadata)curlfor connectivity checks against services the user explicitly asks about
If the user asks for anything that would mutate state, refuse and explain that this skill is read-only.
Step 1: Discovery Phase
Run when no container names were supplied, or when the user explicitly asks "what's running" / "list containers" / similar.
List running containers with a clean, parseable format:
docker ps --format 'table {{.Names}}\t{{.Image}}\t{{.Status}}\t{{.Ports}}'
To include stopped containers as well, add -a:
docker ps -a --format 'table {{.Names}}\t{{.Image}}\t{{.Status}}'
Present the list to the user and ask which containers they'd like to tail. If there are obvious candidates based on the user's stated goal (e.g. they mentioned a service name that matches a container), suggest those by name.
Step 2: Tail Logs
For each container the user selected (or supplied as arguments), start a background log stream. Launch all streams in parallel:
docker logs -f --tail 1000 <container-name> 2>&1
# Run with run_in_background: true
Repeat one invocation per container. Tell the user which streams are running and that you'll check them as needed.
Use Read on the background output files to inspect logs during the session. When the user describes a symptom, grep through the captured output rather than re-tailing.
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 · 96 lines · 68 tokens per session scan A 06bd9b21d11f
local-docker-debug is a skill published in the GitHub repository kolodkin/devpowers (2 stars, last pushed 2d ago), licensed MIT. It adds 68 tokens to every session and 986 once invoked, about $0.0003 per session on Opus 5.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
hermes-s6-container-supervision
Modify or debug s6 services in the Hermes Docker image.
smoke-test
Health smoke tests + auto-fix for gbrain installs (and OpenClaw services when present). Run after machine/container restarts or whenever something seems broken. Tests critical services, auto-fixes bounded local issues, and reports worker topology without starting daemons. Extensible via user-defined test scripts in…
competition-container-runtime
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for live container runtime analysis, mounted secrets, sidecars, namespaces, init containers, entrypoint drift, and route-to-container resolution. Use when the user asks why a live container differs from manifests, where a mounted secret is…
aks-troubleshooting
Debug live Azure Kubernetes Service (AKS) incidents with a read-only, evidence-first investigation. WHEN: pod crashes or Pending, CrashLoopBackOff, OOMKilled, ImagePullBackOff, node NotReady, DNS or ingress failure, connectivity timeout, network policy, SNAT exhaustion, node-pool scaling blocked by QuotaExceeded or…
meta-home-it-rescue
Use this meta-skill instead of answering directly when the user needs help with home, small-team, laptop, browser, printer, Docker, Git, network, UI, or deployment troubleshooting that benefits from multi-skill orchestration across symptom intake, environment capture, web lookup, and repair planning.
aks-gpu-inference
Diagnose Day-2 AKS GPU and KAITO incidents using profile-aware, read-only evidence. WHEN: 'Insufficient nvidia.com/gpu', GPU pod Pending, model-load OOM, DCGM/VRAM, KAITO Workspace not ready, or GPU autoscaling. DO NOT USE FOR: setup (airunway-aks-setup), non-GPU incidents (aks-troubleshooting), standalone VM quota…