Borrowing it
Nothing to install: this file belongs to GitGuardian/ggmcp. 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/GitGuardian/ggmcp/main/.claude/skills/docker-image-tags/SKILL.mdgit clone --depth 1 https://github.com/GitGuardian/ggmcpWrote 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/gitguardian/ggmcp/docker-image-tags)<a href="https://agentmods.dev/skills/gitguardian/ggmcp/docker-image-tags"><img src="https://agentmods.dev/badge/skills/gitguardian/ggmcp/docker-image-tags/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/gitguardian/ggmcp/docker-image-tags"><img src="https://agentmods.dev/badge/skills/gitguardian/ggmcp/docker-image-tags.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00055 | $0.00604 |
| Opus 5.5 | $0.00022 | $0.00242 |
| Sonnet 5.5 | $0.00011 | $0.00121 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade A, and why
docker-image-tags 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 1mo 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Releases and Docker image tags
Releases are release-please-driven: a release-please job in
.github/workflows/release.yml maintains a rolling chore(main): release X.Y.Z PR from conventional commits (version bumps in pyproject.toml,
server.json, and uv.lock, plus CHANGELOG.md — config in
release-please-config.json / .release-please-manifest.json). Merging
that PR is the release: the job creates the vX.Y.Z tag and a draft GitHub
release, builds and signs the image, then publishes the release only after the
image succeeds. CI never pushes commits to main outside the release PR.
Tag matrix and semantics
PUBLISHING.md ("Docker image tag matrix") is canonical for what each event
pushes, what each tag means, and the tag format contract that fixes the shape of
main-<sha>-<seq>. Read it before changing how any tag is built. Short answer to
"which tag do I deploy": X.Y.Z for prod, main-<sha>-<seq> for envs tracking
tip-of-main, never main or latest.
Gotchas
- To release: merge the open release-please PR. Never run
cz bumpor edit version numbers by hand — only release-please writes versions (.release-please-manifest.json+ git tags are canonical). - Tags created in CI with
GITHUB_TOKENdo not trigger workflows: the Docker build must stay in the same workflow run as therelease-pleasejob (aneeds:dependency), never behind anon: push: tagstrigger. - CI checks do not run on the release PR itself (it's created with
GITHUB_TOKEN) — its diff is only version/changelog files. - release-please creates normal releases as drafts; the
create-github-releasejob publishes them only after the image succeeds. It also creates releases for human-pushed escape-hatch tags. It must stay gated on a release tag existing: no-release main pushes still build themainimages and would otherwise try to publish with an empty tag name. - Never tag images with versions that outrank semver releases (e.g. a
CalVer-looking
2026.6.0): downstream semver tracking would consider every real0.x.yrelease "older" and stop proposing updates.
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.
- 1mo ago First seen · 43 lines · 55 tokens per session scan A c95daea50c0f
docker-image-tags is a skill published in the GitHub repository GitGuardian/ggmcp (41 stars, last pushed 4d ago), licensed MIT. It adds 55 tokens to every session and 604 once invoked, about $0.0002 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.
Other skills, from other repositories
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
deploy-akashic
A deployment procedure for an Akashic project that checks and merges an approved pull request, then submits the resulting code revision to update a Docker-based service. The host system handles stopping, moving, and restarting the service.
release-changelog-harness
Chooses ecosystem-native release and changelog tooling (Changesets, Melos, release-plz) plus binary distribution (GitHub Release tarballs, install.sh) when the product is an executable. Use for release CI, install.sh, versioning, CHANGELOGs, shipping MCP/CLI without clone, or meta repos that only ship skills via npx…
polish-docs-meta
Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
release
Used to release all toolbox, integrations, agents. Use when releasing a subproject to PyPI, Docker Hub, or when the user asks to release or publish.