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 chaterm/terminal-skills --skill networkinggit clone --depth 1 https://github.com/chaterm/terminal-skillsWrote 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/chaterm/terminal-skills/networking)<a href="https://agentmods.dev/skills/chaterm/terminal-skills/networking"><img src="https://agentmods.dev/badge/skills/chaterm/terminal-skills/networking/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/chaterm/terminal-skills/networking"><img src="https://agentmods.dev/badge/skills/chaterm/terminal-skills/networking.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.00008 | $0.01647 |
| Opus 5.5 | $0.00003 | $0.00659 |
| Sonnet 5.5 | $0.00002 | $0.00329 |
| Haiku 4.5 | $0.00001 | $0.00165 |
Grade A, and why
networking 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.
apt-get update && apt-get install -y iputils-ping curl netcat-openbsd How it starts
The opening of the file, as written. The whole thing — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker 容器网络
概述
容器网络模式、跨主机通信等技能。
网络驱动
网络类型
# bridge(默认)- 单主机容器通信
# host - 共享主机网络
# none - 无网络
# overlay - 跨主机通信(Swarm)
# macvlan - 分配 MAC 地址
查看网络
# 列出网络
docker network ls
# 网络详情
docker network inspect bridge
docker network inspect network_name
# 查看容器网络
docker inspect container_name --format '{{json .NetworkSettings.Networks}}'
Bridge 网络
默认 bridge
# 容器使用默认 bridge
docker run -d --name web nginx
# 查看 IP
docker inspect web --format '{{.NetworkSettings.IPAddress}}'
# 默认 bridge 容器间通过 IP 通信
# 不支持容器名解析
自定义 bridge
# 创建网络
docker network create mynet
docker network create --driver bridge --subnet 172.20.0.0/16 mynet
# 使用自定义网络
docker run -d --name web --network mynet nginx
docker run -d --name api --network mynet myapi
# 自定义网络支持容器名解析
docker exec api ping web
连接多个网络
# 创建网络
docker network create frontend
docker network create backend
# 容器连接多个网络
docker run -d --name app --network frontend myapp
docker network connect backend app
# 断开网络
docker network disconnect frontend app
Host 网络
# 使用主机网络
docker run -d --network host nginx
# 容器直接使用主机端口
# 无需端口映射
# 性能最好,但端口可能冲突
None 网络
# 无网络
docker run -d --network none myapp
# 完全隔离,无网络访问
# 适用于安全敏感场景
端口映射
# 映射端口
docker run -d -p 8080:80 nginx # HOST:CONTAINER
docker run -d -p 80:80 -p 443:443 nginx # 多端口
docker run -d -p 127.0.0.1:8080:80 nginx # 绑定特定 IP
docker run -d -P nginx # 随机端口
# 查看端口映射
docker port container_name
DNS 配置
# 自定义 DNS
docker run -d --dns 8.8.8.8 nginx
docker run -d --dns 8.8.8.8 --dns 8.8.4.4 nginx
# 自定义主机名
docker run -d --hostname myhost nginx
# 添加 hosts 记录
docker run -d --add-host db:192.168.1.100 nginx
网络别名
# 创建网络
docker network create mynet
# 使用别名
docker run -d --name web --network mynet --network-alias webserver nginx
# 其他容器可通过别名访问
docker run --rm --network mynet busybox ping webserver
Overlay 网络(Swarm)
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 · 274 lines · 8 tokens per session scan A 1a1223f8ea11
networking is a skill published in the GitHub repository chaterm/terminal-skills (59 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 8 tokens to every session and 1,647 once invoked, about $0.0000 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-30.
Other skills, from other repositories
harbor
CLI toolkit for managing containerized LLM services. Use when the user wants to start, stop, configure, or manage AI/LLM services like Ollama, Open WebUI, llama.cpp, vLLM, LiteLLM, ComfyUI, and 250+ others. Triggers on requests to "run a model", "start ollama", "set up an LLM", "configure harbor", "manage services"…
agentbox-info
Spin up isolated sandboxes ("boxes") for coding agents, run them in parallel, queue background runs with -i, and push commits safely through the host relay. Use when the user wants to run Claude Code / Codex / OpenCode in a sandbox, start more boxes, attach to a running box, or otherwise operate the agentbox CLI on…
docker-debugger
Debug Docker containers, fix Dockerfile issues, optimize images, and troubleshoot docker-compose. Use when having Docker problems, container issues, or optimizing Docker builds.
04-security
A security and operations guide for deploying Dify, an open-source platform for building AI applications, in production.
agents-v2-py
Build container-based Foundry Agents with Azure AI Projects SDK (ImageBasedHostedAgentDefinition). Use when creating hosted agents with custom container images in Azure AI Foundry.
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…