Docker MCP Gateway is a Docker CLI plugin that runs and manages Model Context Protocol (MCP) servers, which connect AI applications to external tools, services, databases, and APIs. Developers use it to give multiple AI clients a shared, controlled way to access MCP servers, including isolated containers and authentication flows. The catalogue add-ons support operating and configuring this gateway.
Borrowing it
Nothing to install: this file belongs to docker/mcp-gateway. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/docker/mcp-gateway/main/.claude/skills/otel-instrument/SKILL.mdgit clone --depth 1 https://github.com/docker/mcp-gatewayWrote 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/docker/mcp-gateway/otel-instrument)<a href="https://agentmods.dev/skills/docker/mcp-gateway/otel-instrument"><img src="https://agentmods.dev/badge/skills/docker/mcp-gateway/otel-instrument/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/docker/mcp-gateway/otel-instrument"><img src="https://agentmods.dev/badge/skills/docker/mcp-gateway/otel-instrument.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 253 Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.Fix: Pin the image: image:tag or image@sha256:abc123
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.00102 | $0.02658 |
| Opus 5.5 | $0.00041 | $0.01063 |
| Sonnet 5.5 | $0.00020 | $0.00532 |
| Haiku 4.5 | $0.00010 | $0.00266 |
Grade A, and why
OpenTelemetry Instrumentation Extension 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 2mo 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 — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenTelemetry Instrumentation Extension
Automatically extend OpenTelemetry instrumentation for new functionality in the MCP Gateway, following established patterns documented in docs/telemetry/README.md.
When to Use This Skill
Automatically apply when:
- New state-changing operations added (Create, Update, Delete, Push, Pull, Add, Remove, etc.)
- New CLI commands added to
cmd/docker-mcp/ - New packages with operations in
pkg/ - User mentions "otel", "telemetry", "instrumentation", "metrics", or "tracing"
- Code changes that modify state (database, files, containers, configuration)
- Reviewing code for telemetry coverage
Workflow
Phase 1: Analysis & Suggestion
-
Read project telemetry standards:
- Read
docs/telemetry/README.md"Development Guidelines" section - Read
pkg/telemetry/telemetry.goto understand existing patterns and metrics
- Read
-
Identify scope using git diff:
- Find new/changed files in
pkg/andcmd/docker-mcp/ - Identify functions performing state-changing operations
- Infer domain from package structure (e.g.,
pkg/foo/→ domain:foo)
- Find new/changed files in
-
Categorize findings:
- Operations in existing domains (use existing metrics)
- Operations in new domains (need new metrics)
-
Present suggestions to user:
- List each function needing instrumentation with file:line reference
- Specify operation type (create, update, delete, etc.)
- Identify domain and whether metrics exist
- Show what will be added (instrumentation code, metrics, docs, tests)
Phase 2: Implementation (After User Approval)
Execute in this order:
- Make changes: Instrument operations and add metrics to
pkg/telemetry/telemetry.go - Verify: Build, run with OTEL collector, check
docker logs otel-debugoutput - Write tests: Add tests to
pkg/telemetry/telemetry_test.go - Update docs: Add metrics/operations to
docs/telemetry/README.md - Run tests: Execute
make test - Final verification: Run
./docs/telemetry/testing/test-telemetry.sh
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.
- 2mo ago First seen · 318 lines · 102 tokens per session scan A ed553455382e
OpenTelemetry Instrumentation Extension is a skill published in the GitHub repository docker/mcp-gateway (1,626 stars, last pushed 11d ago), licensed MIT. It adds 102 tokens to every session and 2,658 once invoked, about $0.0004 per session on Opus 5.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-30.
OpenTelemetry Instrumentation Extension compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| OpenTelemetry Instrumentation Extensiondocker/mcp-gateway | Skill | 1.6k | 11d ago | MIT | A | 102 | Claude Code |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 103 | Claude Code |