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 instructions/sondt2709/docker-mcp/docker-modemgit clone --depth 1 https://github.com/sondt2709/docker-mcpWhat 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.00358 | $0.00358 |
| Opus 5 | $0.00179 | $0.00179 |
| Sonnet 5 | $0.00072 | $0.00072 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
docker-mcp docker-modem.instructions.md 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 2d 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.
What it actually says
docker-modem
Docker's Remote API network layer module.
docker-modem will help you interacting with Docker, since it already implements all the network strategies needed to support all Docker's Remote API endpoints.
It is the module powering (network wise) dockerode and other modules.
Usage
Getting started
var Modem = require('docker-modem');
var modem1 = new Modem({socketPath: '/var/run/docker.sock'});
var modem2 = new Modem(); //defaults to above if env variables are not used
var modem3 = new Modem({host: 'http://192.168.1.10', port: 3000});
var modem4 = new Modem({protocol:'http', host: '127.0.0.1', port: 3000});
var modem5 = new Modem({host: '127.0.0.1', port: 3000}); //defaults to http
SSH
You can connect to the Docker daemon via SSH in two ways:
- Using the built-in SSH agent.
- Implement your own custom agent.
//built-in SSH agent
var modem1 = new Modem({
protocol: 'ssh',
host: 'ssh://127.0.0.1',
port: 22
});
//custom agent
var customAgent = myOwnSSHAgent({host: 'ssh://127.0.0.1', port: 22});
var modem2 = new Modem({
agent: customAgent,
});
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.
- 2d ago First seen · 46 lines · 358 tokens per session scan A f73d822b2922
docker-mcp docker-modem.instructions.md is an instructions file published in the GitHub repository sondt2709/docker-mcp (1 stars, last pushed 1y ago), licensed MIT. It adds 358 tokens to every session, about $0.0018 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 instructions, from other repositories
appwrite AGENTS.md
AGENTS.md instructions for appwrite/appwrite, covering appwrite, commands, stack, layout and libraries.
kubevirt-tekton-tasks AGENTS.md
Instructions for kubevirt/kubevirt-tekton-tasks, covering kubevirt tekton tasks - project guide, jira task management, documentation, project structure and key relationships.
docker-zoneminder CLAUDE.md
Instructions for jantman/docker-zoneminder, covering claude.md, project overview, build and test, ci/cd and architecture.
MoaV AGENTS.md
Instructions for MotherofallVPNs/MoaV, covering what moav is, install & run, everyday operations, dashboards & access — what to hand the owner and where things live.
observability-mcp CLAUDE.md
Instructions for ThoTischner/observability-mcp, covering observability-mcp development guide, docker-first development, quick start, rebuild a single service and view logs.
docker-gemini-cli GEMINI.md
Instructions for naoyoshinori/docker-gemini-cli, covering 1. core functionality, 2. project structure and key files, 2.1. image variants, 2.2. automation and 3. documentation.