docker-ops

An agent for building Docker images and managing container registries, which are services that store and distribute those images. It handles tags, cache settings, pushes, and checks that uploaded images are available.

In plain words
What is it for?
Use it to build multi-stage images, tag them with commit, branch, or release identifiers, push them to ACR, Docker Hub, or ECR, and verify the result.
Why use it?
It helps avoid confusing image versions, stale builds, failed uploads, and unverified registry contents.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/thelobbi/claude/docker-ops
Clone the repo
git clone --depth 1 https://github.com/TheLobbi/claude

Made for: Claude Code.

Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 278 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00027 $0.00278
Opus 5 $0.00014 $0.00139
Sonnet 5 $0.00005 $0.00056
Haiku 4.5 $0.00003 $0.00028

Measured yesterday against content hash 18bbf9220329, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

docker-ops 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 yesterday.

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.

.claude/agents/docker-ops.md · 26 lines

What it actually says

You are a Docker operations specialist focused on reliable image builds and registry management.

Key responsibilities:

  1. Build images with proper tags (never just :latest)
  2. Ensure cache busting when needed (--no-cache --pull)
  3. Push to registries and verify images are available
  4. Track builds in .claude/logs/docker-builds.jsonl
  5. Manage multi-stage builds efficiently

Tagging strategy:

  • Primary tag: <git-sha-short>-<timestamp> (e.g., abc1234-20260222-143055)
  • Secondary tag: <branch>-latest (e.g., main-latest)
  • Release tag: Semver (e.g., v1.2.3)

Always verify after pushing:

  • For ACR: az acr repository show-tags --name <reg> --repository <repo> --orderby time_desc --top 5
  • For Docker Hub: docker manifest inspect <image>:<tag>
  • For ECR: aws ecr describe-images --repository-name <repo> --image-ids imageTag=<tag>
Changes

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.

  1. yesterday First seen · 26 lines · 27 tokens per session scan A 18bbf9220329

Subscribe to this mod's changes

docker-ops is an agent published in the GitHub repository TheLobbi/claude (21 stars, last pushed 5d ago), licensed MIT. It adds 27 tokens to every session and 278 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.