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 agentmods add skills/kolodkin/devpowers/ssh-docker-debugnpx skills add kolodkin/devpowers --skill ssh-docker-debuggit clone --depth 1 https://github.com/kolodkin/devpowersWhat 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 | $0.00075 | $0.01007 |
| Opus 5 | $0.00037 | $0.00504 |
| Sonnet 5 | $0.00015 | $0.00201 |
| Haiku 4.5 | $0.00007 | $0.00101 |
Grade B, and why
ssh-docker-debug scanned grade B with 2 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 yesterday.
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.
- If `docker ps` requires sudo on the target VM, prefix the remote command with `sudo` only after confirming with the user; some hosts add the SSH user to the `docker` group and don't need it. 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SSH Docker Debugging
Discover and tail logs for Docker containers on a remote VM over SSH.
Arguments
/ssh-docker-debug <ssh-host> [container-name ...]
- ssh-host (required) — SSH host name as configured in
~/.ssh/config - 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 remote VM. 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)ssh -Gfor host resolutioncurlfor 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: Resolve the VM IP (optional, for curl checks)
ssh -G <ssh-host> | grep "^hostname "
Use the resolved IP for any curl commands later in the session.
Step 2: 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:
ssh <ssh-host> "docker ps --format 'table {{.Names}}\t{{.Image}}\t{{.Status}}\t{{.Ports}}'"
To include stopped containers as well, add -a:
ssh <ssh-host> "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 3: Tail Logs
For each container the user selected (or supplied as arguments), start a background log stream. Launch all streams in parallel:
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.
- yesterday First seen · 99 lines · 75 tokens per session scan B 0e53fcb20c0f
ssh-docker-debug is a skill published in the GitHub repository kolodkin/devpowers (2 stars, last pushed 22d ago), licensed MIT. It adds 75 tokens to every session and 1,007 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…