container-registry

container-registry is an agent for coding agents from ASCIT31/Dark-Moon. It costs 59 tokens per session (6,168 once invoked), scanned A, original, GPL-3.0.

An automated security-testing agent for OCI and Docker container registries, which store and distribute container images. It covers registries such as Harbor, GHCR, GitLab Registry, and cloud registries.

In plain words
What is it for?
It is for testing registry access, permissions, image storage, and related security controls across supported registry services.
Why use it?
It helps find security weaknesses in the systems that hold container images, without requiring separate manual checks for each registry product.

Agent

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/ascit31/dark-moon/container-registry
Clone the repo
git clone --depth 1 https://github.com/ASCIT31/Dark-Moon
Per session 59 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 6,168 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin unknown 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.00059 $0.06168
Opus 5 $0.00030 $0.03084
Sonnet 5 $0.00012 $0.01234
Haiku 4.5 $0.00006 $0.00617

Measured 3d ago against content hash a168ea4c7a38, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

container-registry scanned grade A with 1 finding 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 3d 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.

Makes network callslowCapability

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

the exact HTTP call and its raw response. Use curl+jq against the v2 API and
conf/agents/container-registry.md · 442 lines

The source is not reproduced here

Licensed GPL-3.0

The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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. 3d ago First seen · 442 lines · 59 tokens per session scan A a168ea4c7a38

Subscribe to this mod's changes

container-registry is an agent published in the GitHub repository ASCIT31/Dark-Moon (886 stars, last pushed 5d ago), licensed GPL-3.0. It adds 59 tokens to every session and 6,168 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.