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/evolplus/talos/docker-deploymentnpx skills add evolplus/talos --skill docker-deploymentgit clone --depth 1 https://github.com/evolplus/talosWhat 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.00077 | $0.01078 |
| Opus 5 | $0.00039 | $0.00539 |
| Sonnet 5 | $0.00015 | $0.00216 |
| Haiku 4.5 | $0.00008 | $0.00108 |
Grade A, and why
docker-deployment 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker Deployment
When to use
Use this skill when a DevOps task deploys a Dockerfile, a Docker image, or a Docker Compose stack. For the existing local QA environment flow, keep using local-deployment; use this skill when the task is broader than local QA, especially remote servers, staging-like hosts, image promotion, or compose-based releases.
Inputs and outputs
- Inputs: task ID, target environment, Dockerfile or compose path, image tag or build source, environment contract, safe env templates, target host or SSH alias for remote deploys, and rollback expectation.
- Outputs: built or pulled image evidence, compose validation result, running service health checks, rollback command, and
docs/deploy-reports/<task-id>.mdwith redacted environment evidence.
Procedure
- Classify the target. If the target is local QA, follow
local-deployment. If the target is a remote VM or server, first followssh-remote-operationsfor connectivity, approval, and remote command discipline. If the target is Kubernetes, usekubernetes-deploymentinstead. - Find project-owned Docker assets. Use the task and architecture docs to identify
Dockerfile,compose.yml,docker-compose.yml, or project-owned files underinfra/ordeploy/. Do not create a new reusable infra layout unless the task explicitly asks for it. - Validate environment inputs without secrets. Read safe templates (
.env.example,.env.template,.env.sample) for key names only. Detect.env*presence by path/status only. Usedocker compose config --quiet; never print fulldocker compose configbecause it can expand secrets. - Use deterministic image references. Prefer immutable tags or digests. If building from a Dockerfile, record source commit, build target, platform, and final image tag. Do not deploy
latestto a non-dev environment unless the architecture explicitly allows it. - Scope Compose mutations. Always pass
-p <project-slug>for compose mutations. Use a project-specific release directory on remote hosts, for example/opt/<project-slug>/releases/<task-id-or-version>. Never run global prune commands. - Deploy with a reversible sequence. Pull/build, validate config, start/update services, wait for health checks, then capture logs only when needed and with redaction. Keep the previous image tag or release directory available for rollback.
- Health-check the actual surface. Use declared HTTP health endpoints, container health status, or application smoke probes. "Container is running" is not enough.
- Write the deploy report. Include target environment, host alias (not credentials), compose files, image references, platform, env-file status, health-check results, rollback command, and known limitations. Use names/statuses only for secret-bearing files.
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 · 58 lines · 77 tokens per session scan A cb2378c4a473
docker-deployment is a skill published in the GitHub repository evolplus/talos (8 stars, last pushed 28d ago), licensed Apache-2.0. It adds 77 tokens to every session and 1,078 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
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…