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.
git clone --depth 1 https://github.com/ivegamsft/basecoatWrote 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/agents/ivegamsft/basecoat/basecoat-30-ai-containerization-planner)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-30-ai-containerization-planner"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-30-ai-containerization-planner.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.00074 | $0.00412 |
| Opus 5 | $0.00037 | $0.00206 |
| Sonnet 5 | $0.00015 | $0.00082 |
| Haiku 4.5 | $0.00007 | $0.00041 |
Grade A, and why
containerization-planner 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
Containerization Planner Agent
Guides containerization planning: evaluates workloads against Docker, AKS, and ACA to recommend the optimal deployment platform, then generates production-ready container configurations.
Inputs
- Workload description, current deployment platform, scale and availability requirements
- Team expertise, budget constraints, compliance requirements (optional)
Workflow
- Assess workload readiness: application factors, operational factors, and security factors.
- Select deployment platform: Docker (self-managed), ACA (serverless), or AKS (orchestrated).
- Generate Dockerfile with multi-stage builds, non-root user, and health checks.
- Configure health probes: liveness, readiness, and startup probes with appropriate thresholds.
- Set resource limits and requests based on workload profile (light/medium/heavy).
- Generate platform-specific deployment manifests (Docker Compose, ACA YAML, or AKS Kubernetes).
- Produce implementation checklist: Dockerfile, CI/CD pipeline, image registry, monitoring.
Output
Platform recommendation report, Dockerfile with multi-stage build, health probe configuration, resource limit spec, platform-specific deployment manifest (Docker Compose/ACA/AKS), and implementation checklist.
References
Platform decision criteria, Dockerfile template, health probe configuration, resource profiles, Docker Compose/AKS/ACA manifest examples, readiness assessment factors: agents/references/containerization-planner-detail.md
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 · 42 lines · 74 tokens per session scan A 9cb2a2204c48
containerization-planner is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 2d ago), licensed MIT. It adds 74 tokens to every session and 412 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-09-03.
Other agents, from other repositories
devops-engineer
Deployment and infrastructure expert for .NET — Docker multi-stage builds, GitHub Actions and Azure DevOps pipelines, and .NET Aspire orchestration. Use when containerizing an application, setting up or fixing CI/CD, configuring Aspire AppHost and service defaults, or preparing an app for production deployment.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
incident-commander
Conduz investigação de incidente end-to-end — triagem, preservação de evidência, hipótese, validação e proposta de mitigação. Despachado por /pwdev-devops:incidente. Modelo forte porque correlacionar sintomas sob pressão é onde o raciocínio mais importa. Propõe; nunca executa sozinho.
helm-agent
Executing agent. Writes and maintains Helm charts: Chart.yaml, templates/, values.yaml, helpers. Scope: davinci/kubernetes/apps/helm/, /Chart.yaml, /values.yaml.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
devops-automator
Use this agent when setting up CI/CD pipelines, configuring cloud infrastructure, implementing monitoring systems, or automating deployment processes. This agent specializes in making deployment and operations seamless for rapid development cycles.