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 skills add LuuOW/meridian-mcp --skill docker-registrygit clone --depth 1 https://github.com/LuuOW/meridian-mcpWrote 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/luuow/meridian-mcp/docker-registry)<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.
<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>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.00035 | $0.01927 |
| Opus 5 | $0.00017 | $0.00963 |
| Sonnet 5 | $0.00007 | $0.00385 |
| Haiku 4.5 | $0.00003 | $0.00193 |
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 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
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.
- 9d ago First seen · 241 lines · 35 tokens per session scan B 4c8d4217c310
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.
Other skills, from other repositories
buildah
Buildah OCI container image builder reference. Build container images without Docker daemon. Covers Containerfile builds, scripted builds with shell commands, direct filesystem mount, rootless operation, multi-arch manifests, and CI/CD integration.
deployment
Use when taking an app from source to live: choosing the deploy target from requirements (Hetzner+Coolify vs Vercel vs a third), then wiring container → CI → registry → host with build secrets, healthchecks and rollback. NOT one platform's mechanics (that is coolify, vercel, railway, render), NOT the Dockerfile alone…
bazel-oci-expert
Expert knowledge for building OCI container images with Bazel using rulesoci. Use for containerizing Quarkus/Java applications, multi-arch builds, and image optimization.
dep
Handles containerization, CI/CD pipelines, and deployment setup.
DevOps & Deployment
CI/CD pipelines, containerization, Kubernetes, and infrastructure as code patterns.
image-management
A guide to managing Docker images, the packaged files used to create containers. It covers finding, inspecting, building, tagging, sharing, exporting, importing, and removing images.