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/martian56/claude-engineer/docker-dev-environmentnpx skills add martian56/claude-engineer --skill docker-dev-environmentgit clone --depth 1 https://github.com/martian56/claude-engineerWrote 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/martian56/claude-engineer/docker-dev-environment)<a href="https://agentmods.dev/skills/martian56/claude-engineer/docker-dev-environment"><img src="https://agentmods.dev/badge/skills/martian56/claude-engineer/docker-dev-environment.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 | $0.00046 | $0.00472 |
| Opus 5 | $0.00023 | $0.00236 |
| Sonnet 5 | $0.00009 | $0.00094 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
docker-dev-environment 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 3d 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
Docker Dev Environment
Announce at start: "I'm using claude-engineer:docker-dev-environment to run services in Docker and the app native."
Iron Law
Only stateful services run in Docker. The app (frontend + backend) runs NATIVELY in its own shell.
Rationale: instant uvicorn --reload / next dev / vite HMR, real debuggers, and CI/toolchain parity -
Docker handles only the painful-to-install backing services.
The baseline services (docker-compose.yml)
- PostgreSQL - primary DB (
localhost:5432). - Redis - cache, sessions, rate-limit, job broker (
localhost:6379). - MinIO - S3-compatible object storage (
localhost:9000API /9001console) + a bucket-bootstrap step. - Mailpit - email capture for signup/reset flows (
localhost:1025SMTP /8025UI). All with healthchecks and named volumes. The native app connects vialocalhostURLs in.env.
The dev flow
docker compose up -d(services only).- Backend in shell A:
uv run uvicorn ...(native). - Frontend in shell B:
pnpm dev/bun dev/vite(native).
Non-negotiables
- Never containerize the app for local dev (the guard hook will remind you).
- Healthchecks on every service; the app waits for healthy services.
- Secrets/connection strings via
.env(git-ignored), documented.
Full detail (the complete compose file, MinIO bucket bootstrap, Mailpit SMTP config, connection settings):
read references/dev-services.md on demand.
Red flags - STOP
docker compose upthat builds/starts the app itself for local dev.- Hardcoded service URLs instead of
.env. - A service with no healthcheck.
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.
- 3d ago First seen · 39 lines · 46 tokens per session scan A 83041f2eaad0
docker-dev-environment is a skill published in the GitHub repository martian56/claude-engineer (2 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 472 once invoked, about $0.0002 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
deploy-registry-server-with-cnpg
Deploy the ToolHive Registry Server to a Kind cluster with CloudNativePG (CNPG) PostgreSQL database. Use when you need a production-like PostgreSQL setup with the CNPG operator.
cnpg
Create and operate CloudNativePG (CNPG) Postgres databases on Kubernetes the GitOps/Flux way - on managed cloud (GKE + GCS via Workload Identity) OR self-hosted (K3s/bare-metal + any S3-compatible store via a credentials secret). Covers Cluster + ScheduledBackup manifests, barman WAL archiving, pgvector, PITR…
alloydb-omni-container
You're an expert in AlloyDB Omni running in a container. You can help users with related tasks such as starting, stopping, listing, connecting to AlloyDB Omni instance running in a container, and querying for logs.
vps-maintenance
Install or update a recurring VPS housekeeping pack on any Linux + Docker VPS — daily Postgres logical backups, weekly Docker prune, weekly DB retention cleanup, and a 5-min memory pressure alert to Slack or Telegram. Use when the user says "set up vps maintenance", "/vps-maintenance", "install housekeeping crons"…
using-relational-databases
Relational database implementation across Python, Rust, Go, and TypeScript. Use when building CRUD applications, transactional systems, or structured data storage. Covers PostgreSQL (primary), MySQL, SQLite, ORMs (SQLAlchemy, Prisma, SeaORM, GORM), query builders (Drizzle, sqlc, SQLx), migrations, connection pooling…
Docker Testcontainers
Integration testing with real dependencies in throwaway Docker containers using the Testcontainers Node.js API - GenericContainer, exposed ports, wait strategies, module containers, Docker Compose environments, and reliable cleanup.