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 Goodsmileduck/claude-registry --skill digitalocean-registry-cleanupgit clone --depth 1 https://github.com/Goodsmileduck/claude-registryWrote 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/goodsmileduck/claude-registry/digitalocean-registry-cleanup)<a href="https://agentmods.dev/skills/goodsmileduck/claude-registry/digitalocean-registry-cleanup"><img src="https://agentmods.dev/badge/skills/goodsmileduck/claude-registry/digitalocean-registry-cleanup/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/goodsmileduck/claude-registry/digitalocean-registry-cleanup"><img src="https://agentmods.dev/badge/skills/goodsmileduck/claude-registry/digitalocean-registry-cleanup.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.00081 | $0.00398 |
| Opus 5 | $0.00041 | $0.00199 |
| Sonnet 5 | $0.00016 | $0.00080 |
| Haiku 4.5 | $0.00008 | $0.00040 |
Grade A, and why
digitalocean-registry-cleanup 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 11d 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.
What it actually says
DigitalOcean Registry Cleanup
Prerequisite: doctl CLI must be installed and authenticated (doctl auth init).
Script
Run scripts/registry_cleanup.py via Bash tool:
SCRIPT="<skill-path>/scripts/registry_cleanup.py"
# Analyze: show all repos with tag counts and dates
python3 $SCRIPT analyze
# Clean: delete old tags from a repo, keep newest N
python3 $SCRIPT clean <repo> --keep 5 --dry-run # preview first
python3 $SCRIPT clean <repo> --keep 5 # execute
# Stale: find repos not updated in N months
python3 $SCRIPT stale --months 6 # list only
python3 $SCRIPT stale --months 6 --delete # delete all tags
# GC: trigger garbage collection to reclaim storage
python3 $SCRIPT gc
Workflow
- Run
analyzeto show registry overview - Present the table to the user, ask which repos to clean and how many tags to keep
- Run
clean <repo> --keep N --dry-runto preview - On user confirmation, run
clean <repo> --keep Nto delete - Run
staleif user wants to find abandoned repos - Run
gcafter all deletions to reclaim storage - Run
analyzeagain to show the result
Always use --dry-run first before destructive operations.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 43 lines · 81 tokens per session scan A 2bf959174d3e
digitalocean-registry-cleanup is a skill published in the GitHub repository Goodsmileduck/claude-registry (1 stars, last pushed 1mo ago), licensed MIT. It adds 81 tokens to every session and 398 once invoked, about $0.0004 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.
Other skills, from other repositories
docker-management
Manage Docker containers, images, volumes, and Compose.
hermes-s6-container-supervision
Modify or debug s6 services in the Hermes Docker image.
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
docker-patterns
Docker and Docker Compose patterns for local development, container security, networking, volume strategies, and multi-service orchestration. Use when setting up containerized development environments or reviewing Docker configurations.
github-actions-templates
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
scanning-containers-with-trivy-in-cicd
This skill covers integrating Aqua Security's Trivy scanner into CI/CD pipelines for comprehensive container image vulnerability detection. It addresses scanning Docker images for OS package and application dependency CVEs, detecting misconfigurations in Dockerfiles, scanning filesystem and git repositories, and…