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/cn-big-cabbage/github-skill-distiller/lazydockernpx skills add CN-big-cabbage/github-skill-distiller --skill lazydockergit clone --depth 1 https://github.com/CN-big-cabbage/github-skill-distillerWrote 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/cn-big-cabbage/github-skill-distiller/lazydocker)<a href="https://agentmods.dev/skills/cn-big-cabbage/github-skill-distiller/lazydocker"><img src="https://agentmods.dev/badge/skills/cn-big-cabbage/github-skill-distiller/lazydocker.svg" alt="Measured on agentmods" 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.00021 | $0.01164 |
| Opus 5 | $0.00010 | $0.00582 |
| Sonnet 5 | $0.00004 | $0.00233 |
| Haiku 4.5 | $0.00002 | $0.00116 |
Grade A, and why
lazydocker 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 5d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
lazydocker Docker 终端 UI 管理助手
技能概述
本技能帮助用户通过 lazydocker 的终端 UI 界面管理 Docker 容器、镜像、卷和网络，支持以下场景：
- 容器管理: 查看、启动、停止、重启、删除容器，实时查看日志和资源占用
- 镜像管理: 列出、拉取、删除镜像，查看镜像层信息
- 卷管理: 查看和删除 Docker 卷
- Docker Compose: 管理 Compose 服务的完整生命周期
- 实时监控: 查看 CPU、内存、网络 I/O 等实时统计信息
支持平台: macOS、Linux、Windows（WSL2）、Docker Desktop
使用流程
AI 助手将引导你完成以下步骤：
- 检查并安装 lazydocker（如未安装）
- 确认 Docker 守护进程正在运行
- 启动 lazydocker 并进入 TUI 界面
- 根据需求执行容器/镜像/卷操作
- 验证操作结果
关键章节导航
AI 助手能力
当你向 AI 描述 Docker 管理需求时，AI 会：
- 自动检测系统环境并安装 lazydocker
- 验证 Docker 守护进程状态
- 指导键盘快捷键操作
- 解析容器/镜像/卷的状态信息
- 协助调试容器启动失败问题
- 生成 Docker Compose 配置并通过 lazydocker 管理服务
核心功能
- 容器面板：查看所有容器状态、日志、统计信息
- 镜像面板：浏览本地镜像，支持删除和拉取
- 卷面板：管理 Docker 持久化卷
- 服务面板：Docker Compose 服务管理（需在 compose 项目目录启动）
- 网络面板：查看 Docker 网络配置
- 实时日志：容器日志流式展示，支持搜索
- 自定义命令：支持在 config.yml 中配置自定义操作
- 键盘驱动：完整键盘导航，无需鼠标
界面布局
┌─────────────────────────────────────────────────────────────┐
│ Containers │ Services │ Images │ Volumes │ Networks │
├─────────────┴───────────┴─────────┴──────────┴──────────────┤
│ 左侧面板：列表视图 │
│ container1 running nginx:latest │
│ container2 exited redis:7.0 │
├──────────────────────────────────────────────────────────────┤
│ 右侧面板：详情/日志/统计 │
│ [Logs] [Stats] [Config] [Env] [Exec] │
└──────────────────────────────────────────────────────────────┘
常用键盘快捷键速查
| 按键 | 功能 |
|---|---|
[ / ] |
切换左侧面板标签（容器/服务/镜像/卷/网络） |
↑ / ↓ |
在列表中上下移动 |
← / → |
切换右侧详情标签 |
enter |
进入容器（exec bash/sh） |
s |
停止容器 |
r |
重启容器 |
d |
删除容器/镜像/卷 |
u |
拉取最新镜像（在服务面板） |
l |
查看日志 |
e |
打开文件编辑器 |
x |
显示可用命令菜单 |
q |
退出 lazydocker |
? |
打开帮助界面 |
快速示例
# 启动 lazydocker
lazydocker
# 在项目目录中启动（自动识别 Docker Compose）
cd /path/to/compose-project && lazydocker
# 指定 Docker 上下文
DOCKER_HOST=tcp://remote-host:2375 lazydocker
What ships with it
4 files 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.
- 5d ago First seen · 126 lines · 21 tokens per session scan A 47e1f93bfba5
lazydocker is a skill published in the GitHub repository CN-big-cabbage/github-skill-distiller (4 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 1,164 once invoked, about $0.0001 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
infra-containers-kubernetes
Kubernetes manifests, Helm charts, Kustomize overlays, and resource patterns.
infra-ci-cd-docker
Docker containerization patterns for Node.js/TypeScript development and production.
docker-management
Docker containers, images, volumes, networks (CLI + Dockerode).
docker-build-deploy
Use when containerizing a Node.js app and setting up GitHub Actions CI/CD to build, push to GHCR, and deploy via SSH. Multi-stage build, non-root user, caching.
ai-assist-dockerize-website
Guide the user through containerizing and serving a simple website or documentation folder with Docker — inspects the project to detect what to serve (ready-to-serve static HTML, a buildable site that emits static output, or a raw markdown/docs folder that needs rendering), generates a Dockerfile, .dockerignore…
docker-kubernetes
Production Docker and Kubernetes patterns including multi-stage builds, minimal base images, non-root users, layer caching, docker-compose for development, K8s Deployments, Services, Ingress, ConfigMaps, Secrets, health checks, resource limits, HPA autoscaling, security contexts, and Helm chart basics. Use when…