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 agentmods add skills/imoonkey/openweb/docker-hubnpx skills add imoonkey/openweb --skill docker-hubgit clone --depth 1 https://github.com/imoonkey/openwebWhat 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 | $0.00000 | $0.00533 |
| Opus 5 | $0.00000 | $0.00267 |
| Sonnet 5 | $0.00000 | $0.00107 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
docker-hub 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 2d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker Hub
Overview
Container image registry. Public REST API for searching and browsing Docker images, tags, and metadata.
Workflows
Find a container image
searchImages(query)→repo_name(format: namespace/name)getImage(namespace, name)→ full description, stars, pull count
Check available versions/tags
searchImages(query)→repo_name→ split intonamespace,namegetTags(namespace, name)→ tags with size, architecture, last updated
Inspect an official image
getImage("library", name)→ image detail (official images use "library" namespace)getTags("library", name)→ available tags
Operations
| Operation | Intent | Key Input | Key Output | Notes |
|---|---|---|---|---|
| searchImages | find container images | query | repo_name, short_description, star_count, pull_count, is_official | entry point, paginated |
| getImage | image details | namespace, name <- searchImages | description, full_description, star_count, pull_count, last_updated | use "library" for official images |
| getTags | list image tags/versions | namespace, name <- searchImages | name, full_size, images[].architecture, last_updated | paginated, orderable |
Quick Start
# Search for images
openweb docker-hub exec searchImages '{"query":"nginx"}'
# Get details for an official image (namespace = "library")
openweb docker-hub exec getImage '{"namespace":"library","name":"nginx"}'
# Get details for a user image
openweb docker-hub exec getImage '{"namespace":"bitnami","name":"nginx"}'
# List tags for an image
openweb docker-hub exec getTags '{"namespace":"library","name":"python","page_size":10}'
# List tags sorted by most recently updated
openweb docker-hub exec getTags '{"namespace":"library","name":"node","ordering":"-last_updated","page_size":25}'
Known Issues
- Official images require
libraryas the namespace parameter. - Search results use
repo_namewhich may belibrary/nginxoruser/repoformat. - Tag
full_sizemay be 0 for multi-arch manifests; checkimages[].sizefor per-architecture sizes. - Pagination defaults vary: search defaults to 25, tags defaults to 10.
What ships with it
8 files 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.
- 2d ago First seen · 52 lines · 0 tokens per session scan A 6c39c5c0f4bf
docker-hub is a skill published in the GitHub repository imoonkey/openweb (56 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 533 tokens. 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…