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 commands/l337-org/docker-mcp/docker-sdkgit clone --depth 1 https://github.com/L337-org/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.00000 | $0.01104 |
| Opus 5 | $0.00000 | $0.00552 |
| Sonnet 5 | $0.00000 | $0.00221 |
| Haiku 4.5 | $0.00000 | $0.00110 |
Grade A, and why
docker-sdk 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker SDK Reference Check
This skill fetches and cross-references the Docker SDK for Python documentation to:
- Verify that any SDK function or class you plan to use actually exists
- Identify which SDK features are not yet exposed in this MCP server
Instructions
When invoked (with or without a specific topic argument), do the following steps IN ORDER. Do not skip steps.
Step 1 - Fetch the SDK documentation
Fetch the top-level API reference to get the list of available modules:
- https://docker-py.readthedocs.io/en/stable/index.html
- https://docker-py.readthedocs.io/en/stable/client.html
- https://docker-py.readthedocs.io/en/stable/containers.html
- https://docker-py.readthedocs.io/en/stable/images.html
- https://docker-py.readthedocs.io/en/stable/volumes.html
- https://docker-py.readthedocs.io/en/stable/networks.html
- https://docker-py.readthedocs.io/en/stable/services.html
- https://docker-py.readthedocs.io/en/stable/secrets.html
- https://docker-py.readthedocs.io/en/stable/configs.html
- https://docker-py.readthedocs.io/en/stable/nodes.html
- https://docker-py.readthedocs.io/en/stable/swarm.html
- https://docker-py.readthedocs.io/en/stable/plugins.html
If the user passed an argument (e.g., /docker-sdk containers), only fetch the page(s) relevant to that topic.
Step 2 - Inventory what this MCP server currently exposes
The project structure maps SDK domains to tool files one-to-one:
| docker_mcp/tools/ file | tests/ file | Docker SDK domain |
|---|---|---|
docker_mcp/tools/system.py |
tests/test_system.py |
DockerClient |
docker_mcp/tools/containers.py |
tests/test_containers.py |
Containers |
docker_mcp/tools/images.py |
tests/test_images.py |
Images |
docker_mcp/tools/networks.py |
tests/test_networks.py |
Networks |
docker_mcp/tools/volumes.py |
tests/test_volumes.py |
Volumes |
docker_mcp/tools/configs.py |
tests/test_configs.py |
Swarm Configs |
docker_mcp/tools/nodes.py |
tests/test_nodes.py |
Swarm Nodes |
docker_mcp/tools/plugins.py |
tests/test_plugins.py |
Plugins |
docker_mcp/tools/prompts.py |
tests/test_prompts.py |
@mcp.prompt() templates for common docker workflows |
docker_mcp/tools/resources.py |
tests/test_resources.py |
@mcp.resource() endpoints for the Docker SDK for Python docs |
docker_mcp/tools/secrets.py |
tests/test_secrets.py |
Swarm Secrets |
docker_mcp/tools/services.py |
tests/test_services.py |
Swarm Services |
docker_mcp/tools/swarm.py |
tests/test_swarm.py |
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.
- 2d ago First seen · 91 lines · 0 tokens per session scan A bf1e0d56e3ce
docker-sdk is a command published in the GitHub repository L337-org/docker-mcp (4 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,104 tokens. 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 commands, from other repositories
web3-audit
Smart contract security audit — runs through 10 bug class checklist (accounting desync, access control, incomplete path, off-by-one, oracle errors, ERC4626, reentrancy, flash loan, signature replay, proxy/upgrade). Applies pre-dive kill signals first. Generates Foundry PoC template for confirmed findings. Usage…
recon
Run full recon pipeline on a target — subdomain enum (Chaos API + subfinder), live host discovery (dnsx + httpx), URL crawl (katana + waybackurls + gau), gf pattern classification, nuclei scan. Outputs to recon/ / directory. Usage: /recon target.com.
report
Write a submission-ready bug bounty report. Generates H1/Bugcrowd/Intigriti/Immunefi format with CVSS 3.1 score, proof of concept, impact statement, and remediation. Run /validate first. Usage: /report.
scope
Check if a target asset is in scope for the program before hunting or submitting. Reads program scope page, checks asset against in-scope and out-of-scope lists, verifies the asset is owned by the target organization. Usage: /scope.
triage
Quick 7-Question Gate triage on a finding before writing a report. Kills N/A submissions before they happen. Faster than /validate — for quick go/no-go decisions. Usage: /triage.
validate
Validate a finding — runs 7-Question Gate + 4-gate checklist. Kills weak findings before report writing. Prevents N/A submissions that hurt validity ratio. Usage: /validate.