docker-registry

docker-registry is a skill for Claude Code, Codex from LuuOW/meridian-mcp. It costs 35 tokens per session (1,927 once invoked), scanned B, original, MIT.

Guidance for storing and managing Docker container images in registries such as GitHub Container Registry, Docker Hub, or a private registry. A container image is a packaged application that can be run by Docker.

In plain words
What is it for?
Use it when setting up registry login, image tagging, CI push pipelines, image cleanup, or publishing images for multiple hardware platforms.
Why use it?
It helps keep image names and versions traceable, supports rollback to earlier builds, and documents how automated builds push images safely.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when setting up registry login, image tagging, CI push pipelines, image cleanup, or publishing images for multiple hardware platforms.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/luuow/meridian-mcp/docker-registry
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.

Any agent
npx skills add LuuOW/meridian-mcp --skill docker-registry
Clone the repo
git clone --depth 1 https://github.com/LuuOW/meridian-mcp

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for docker-registry

README.md
[![agentmods](https://agentmods.dev/badge/skills/luuow/meridian-mcp/docker-registry/github.svg)](https://agentmods.dev/skills/luuow/meridian-mcp/docker-registry)
Your own site
<a href="https://agentmods.dev/skills/luuow/meridian-mcp/docker-registry"><img src="https://agentmods.dev/badge/skills/luuow/meridian-mcp/docker-registry/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.

agentmods 80×15 button for docker-registry

Your own site · 80×15
<a href="https://agentmods.dev/skills/luuow/meridian-mcp/docker-registry"><img src="https://agentmods.dev/badge/skills/luuow/meridian-mcp/docker-registry.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,927 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00035 $0.01927
Opus 5 $0.00017 $0.00963
Sonnet 5 $0.00007 $0.00385
Haiku 4.5 $0.00003 $0.00193

Measured 9d ago against content hash 4c8d4217c310, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade B, and why

docker-registry scanned grade B with 2 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 9d 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

# For systemd/cron jobs that run as root, this works automatically after login

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s http://localhost:5000/v2/_catalog | jq
skills/docker-registry/SKILL.md · 241 lines

How it starts

The opening of the file, as written. The whole thing — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.

docker-registry

Production patterns for pushing, pulling, tagging, and managing container images in registries. Covers GitHub Container Registry (GHCR), Docker Hub, and self-hosted registries.

Tagging Strategy

A good tagging strategy enables rollback, traceability, and cache reuse.

SHA=$(git rev-parse --short HEAD)
BRANCH=$(git rev-parse --abbrev-ref HEAD | sed 's|/|-|g')
TAG_LATEST="ghcr.io/myorg/myapp:latest"
TAG_SHA="ghcr.io/myorg/myapp:${SHA}"
TAG_BRANCH="ghcr.io/myorg/myapp:${BRANCH}"

# Build once, tag multiple times
docker build -t "$TAG_LATEST" .
docker tag "$TAG_LATEST" "$TAG_SHA"
docker tag "$TAG_LATEST" "$TAG_BRANCH"

# Push all tags
docker push "$TAG_LATEST"
docker push "$TAG_SHA"
docker push "$TAG_BRANCH"
Tag Pattern Use
:latest Always current main Default pull for deployments
:<git-sha> abc1234 Immutable — use for rollback
:<branch> feature-auth PR preview environments
:<semver> v2.4.1 Release pinning in external consumers

GitHub Container Registry (GHCR)

# .github/workflows/build-push.yml
name: Build and Push

on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

env:
  REGISTRY: ghcr.io
  IMAGE_NAME: ${{ github.repository }}   # e.g. myorg/myapp

jobs:
  build-push:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      packages: write

    steps:
      - uses: actions/checkout@v4

      - name: Log in to GHCR
        uses: docker/login-action@v3
        with:
          registry: ghcr.io
          username: ${{ github.actor }}
          password: ${{ secrets.GITHUB_TOKEN }}   # no extra secret needed

      - name: Extract metadata
        id: meta
        uses: docker/metadata-action@v5
        with:
          images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
          tags: |
            type=sha,prefix=
            type=ref,event=branch
            type=raw,value=latest,enable=${{ github.ref == 'refs/heads/main' }}

      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v3

      - name: Build and push
        uses: docker/build-push-action@v5
        with:
          context: .
          push: ${{ github.event_name == 'push' }}   # don't push on PRs
          tags: ${{ steps.meta.outputs.tags }}
          labels: ${{ steps.meta.outputs.labels }}
          cache-from: type=gha
          cache-to: type=gha,mode=max

Read the full file on GitHub · 241 lines

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. 9d ago First seen · 241 lines · 35 tokens per session scan B 4c8d4217c310

Subscribe to this mod's changes

docker-registry is a skill published in the GitHub repository LuuOW/meridian-mcp (0 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 1,927 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.