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 docxology/template --skill dockergit clone --depth 1 https://github.com/docxology/templateWrote 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/docxology/template/docker)<a href="https://agentmods.dev/skills/docxology/template/docker"><img src="https://agentmods.dev/badge/skills/docxology/template/docker/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/docxology/template/docker"><img src="https://agentmods.dev/badge/skills/docxology/template/docker.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.00044 | $0.00266 |
| Opus 5.5 | $0.00018 | $0.00106 |
| Sonnet 5.5 | $0.00009 | $0.00053 |
| Haiku 4.5 | $0.00004 | $0.00027 |
Grade A, and why
infrastructure-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 1mo 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
Skill Descriptor — infrastructure/docker
Module Overview
Containerization assets for running the template in a consistent environment.
Capabilities
- Docker container build:
Dockerfileprovides a reproducible build environment - Multi-service orchestration:
docker-compose.ymlmanages dev environment and optional Ollama
Use Cases
- Local development: Run pipeline in container for consistent environment
- Cloud deployment: Deploy using Docker for reproducibility
- Ollama integration: Optional LLM support via docker-compose
Integration Points
- Referenced by
docs/CLOUD_DEPLOY.mdfor headless and container deployment - Invoked directly via
docker build/docker compose(not wired into the default Python pipeline stages)
See Also
What ships with it
4 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.
- 1mo ago First seen · 33 lines · 44 tokens per session scan A 355c12cd54ca
infrastructure-docker is a skill published in the GitHub repository docxology/template (20 stars, last pushed 2d ago), licensed Apache-2.0. It adds 44 tokens to every session and 266 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
dokploy-deploy
This skill should be used when user asks to "deploy with Dokploy", "use Dokploy Cloud", "manage self-hosted Dokploy", "deploy Docker Compose on Dokploy", "manage Dokploy databases", "configure Dokploy domains", or "look up Dokploy CLI commands".
cloudron-app-packaging
Official Cloudron app packaging skill - Dockerfile patterns, manifest, addons, build methods.
planning-with-files
Persistent file-based planning for multi-step AI-agent work. Keeps taskplan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and…
bopomofo-rescue
A text-recovery tool for Taiwanese Bopomofo, also called Zhuyin, keyboard mistakes. It converts letter-and-number sequences typed with the wrong input mode back into likely Chinese text.
devops-infrastructure
Guides Docker, CI/CD pipelines, deployment strategies, infrastructure as code, and observability setup. Use when writing Dockerfiles, configuring GitHub Actions, planning deployments, setting up monitoring, or when asked about containers, pipelines, Terraform, or production infrastructure.
qdrant-deployment-options
Guides Qdrant deployment selection. Use when someone asks 'how to deploy Qdrant', 'Docker vs Cloud', 'local mode', 'embedded Qdrant', 'Qdrant EDGE', 'which deployment option', 'self-hosted vs cloud', or 'need lowest latency deployment'. Also use when choosing between deployment types for a new project.