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 commands/sagargupta16/claude-skills/dockerizegit clone --depth 1 https://github.com/Sagargupta16/claude-skillsWrote 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/commands/sagargupta16/claude-skills/dockerize)<a href="https://agentmods.dev/commands/sagargupta16/claude-skills/dockerize"><img src="https://agentmods.dev/badge/commands/sagargupta16/claude-skills/dockerize.svg" alt="Measured on agentmods" 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.00012 | $0.00318 |
| Opus 5 | $0.00006 | $0.00159 |
| Sonnet 5 | $0.00002 | $0.00064 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
dockerize 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 6d 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
Create Docker configuration for the current project.
Steps:
- Detect project type and runtime:
package.json-> Node.js (check for build script, framework)requirements.txt/pyproject.toml-> Python (check for FastAPI, Flask, Django)Cargo.toml-> Rustgo.mod-> Go- Static HTML/CSS/JS -> Nginx
- Check for existing Docker files:
- If
Dockerfileexists, review and suggest improvements - If not, generate using docker-deploy skill templates
- If
- Generate files:
Dockerfile(multi-stage build, non-root user, optimized layers).dockerignore(exclude .git, .env, node_modules, etc.)docker-compose.yml(dev setup with database if needed)
- If the project uses a database, add the appropriate service:
- MongoDB, PostgreSQL, MySQL, Redis
- Include health checks and persistent volumes
- Show generated files for review before writing
- Verify: if Docker is available, run
docker compose build(ordocker build .) and report the result --docker compose configonly validates YAML syntax. If Docker is unavailable, state explicitly that only config-level validation was performed
Use the docker-deploy skill for all patterns and best practices.
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.
- 6d ago First seen · 29 lines · 12 tokens per session scan A 6bbc347ab536
dockerize is a command published in the GitHub repository Sagargupta16/claude-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 318 once invoked, about $0.0001 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 commands, from other repositories
build-image
Build a Docker image with best practices for caching, security, and size optimization.
debug-pod
Debug a failing or unhealthy Kubernetes pod by analyzing events, logs, and configuration.
k8s-manifest
Generate production-ready Kubernetes manifests for the current application.
create-chart
Generate a Helm chart for deploying an application to Kubernetes.
update-status
Update the status and progress of Linear tickets.
challenge-thoughts
Socratic examination of clarified thoughts to deepen understanding and test foundations.