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/hamchowderr/braynee/dockernpx skills add hamchowderr/braynee --skill dockergit clone --depth 1 https://github.com/hamchowderr/brayneeWhat 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.00091 | $0.01082 |
| Opus 5 | $0.00046 | $0.00541 |
| Sonnet 5 | $0.00018 | $0.00216 |
| Haiku 4.5 | $0.00009 | $0.00108 |
Grade A, and why
docker 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 yesterday.
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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker — local dev ops
Drive Docker from the terminal for everyday dev work: containers, images, Compose
stacks, Docker Desktop lifecycle, and cleanup. Everything is docker … (Compose is
docker compose, Desktop is docker desktop).
Scope: local CLI ops only. This does not wire up Docker's MCP servers — Docker ships its own Claude Code plugin for that (
docker/claude-plugins→docker-mcp-toolkit, ordocker mcp client connect claude-code). Full command catalog, networks/volumes, and troubleshooting are inreference.md.
First — is the daemon up?
docker info >/dev/null 2>&1 && echo "Docker running" || echo "Docker NOT running"
docker desktop status # Docker Desktop state
docker desktop start # start Desktop if it's down
Containers
docker ps # running
docker ps -a # include stopped
docker run --rm -it IMAGE # throwaway interactive container
docker logs -f NAME # follow logs
docker exec -it NAME sh # shell in (try bash if sh missing)
docker stop NAME && docker rm NAME
docker inspect NAME # full config/state JSON
Images
docker images # list
docker build -t NAME:TAG . # build from ./Dockerfile
docker pull IMAGE:TAG
docker rmi IMAGE # remove
Compose (multi-container stacks)
docker compose up -d # start detached
docker compose ps # stack status
docker compose logs -f SERVICE # follow one service
docker compose down # stop + remove (add -v to also drop volumes)
docker compose up -d --build SERVICE # rebuild + restart one service
Docker Desktop lifecycle (docker desktop)
docker desktop status | start | stop | restart
docker desktop update # apply updates
docker desktop engine ls # (Windows) list container engines
Free up space (safe → aggressive)
docker system df # what's using space
docker container prune # remove stopped containers
docker image prune # remove dangling images
docker system prune # stopped containers + dangling images + unused nets
docker system prune -a --volumes # AGGRESSIVE: also unused images + volumes
Always warn before
prune -a --volumes— it deletes unused images and volumes (data loss). Confirm with the user first.
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.
- yesterday First seen · 102 lines · 91 tokens per session scan A 7178ba4996ed
docker is a skill published in the GitHub repository hamchowderr/braynee (2 stars, last pushed 5d ago), licensed MIT. It adds 91 tokens to every session and 1,082 once invoked, about $0.0005 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
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…