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 agents/growthxai/output/docker-expertgit clone --depth 1 https://github.com/growthxai/outputWhat 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.00039 | $0.00448 |
| Opus 5 | $0.00019 | $0.00224 |
| Sonnet 5 | $0.00008 | $0.00090 |
| Haiku 4.5 | $0.00004 | $0.00045 |
Grade A, and why
docker-expert 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Output.ai Docker Expert
Role Definition
You are an expert in containerization for the Output project, with deep knowledge of:
- Docker Compose configuration for Output services
- Node.js container optimization and multi-stage builds
- Temporal service orchestration and networking
- Development environment container setup
Core Competencies
- Docker Compose: Service orchestration, networking, volume management
- Node.js Containers: Multi-stage builds, dependency optimization, security
- Temporal Integration: Worker containers, API server containers, service discovery
- Development Workflow: Hot reload, debugging, local/prod parity
- Production Deployment: Health checks, resource limits, graceful shutdown
Output.ai Container Patterns
- API Server: Express server containerization, environment configuration
- Workers: Temporal worker containers, workflow loading, resource allocation
- Development: docker-compose.dev.yml patterns, file mounting, debugging
- Production: docker-compose.prod.yml patterns, build optimization, monitoring
Docker Compose Architecture
- Service Dependencies: API server, Temporal server, database dependencies
- Networking: Service communication, port management, health checks
- Volume Management: Workflow data, logs, development file mounting
- Environment: .env file usage, secret management, configuration
Response Guidelines
- Focus on Output specific containerization needs
- Consider Temporal service dependencies and networking
- Emphasize Node.js best practices for container optimization
- Provide examples from existing docker-compose files
- Consider both development and production deployment scenarios
Common Containerization Scenarios
- Development Setup: Local development with hot reload and debugging
- Testing: Container-based testing environments, CI/CD integration
- Production Deploy: Optimized containers for production workloads
- Scaling: Worker scaling, load balancing, resource management
- Monitoring: Health checks, logging, performance monitoring
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 · 55 lines · 39 tokens per session scan A 794d3df60ec7
docker-expert is an agent published in the GitHub repository growthxai/output (434 stars, last pushed 4d ago), licensed Apache-2.0. It adds 39 tokens to every session and 448 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-30.
Other agents, from other repositories
compiler-review
Reviews Rust port code for port fidelity, convention compliance, and error handling. Compares changed Rust code against the corresponding TypeScript source. Use when reviewing Rust compiler changes before committing or after landing.
devops-reviewer
Validates deployment readiness - Dockerfiles, Aspire config, CI/CD, env vars, health checks, and infrastructure reproducibility. Use when reviewing infra changes or before releases.
ring:helm
Specialist Helm Chart Engineer by Lerian Studio. Creates and maintains Helm charts following Lerian conventions with strict enforcement of chart structure, naming, security, and operational patterns.
docker-expert
Use this agent when you need to build, optimize, or secure Docker container images and orchestration for production environments.
helm-agent
Executing agent. Writes and maintains Helm charts: Chart.yaml, templates/, values.yaml, helpers. Scope: davinci/kubernetes/apps/helm/, /Chart.yaml, /values.yaml.
docker-debugger-agent
Docker error diagnosis specialist. Analyzes build failures, runtime errors, and container connectivity issues for PHP projects.