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/andrewaltimit/template-repo/containerization-strategygit clone --depth 1 https://github.com/AndrewAltimit/template-repoWrote 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/andrewaltimit/template-repo/containerization-strategy)<a href="https://agentmods.dev/agents/andrewaltimit/template-repo/containerization-strategy"><img src="https://agentmods.dev/badge/agents/andrewaltimit/template-repo/containerization-strategy.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.00000 | $0.01467 |
| Opus 5 | $0.00000 | $0.00733 |
| Sonnet 5 | $0.00000 | $0.00293 |
| Haiku 4.5 | $0.00000 | $0.00147 |
Grade B, and why
containerization-strategy scanned grade B with 2 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 5d 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.
Downloads and executes remote codemediumSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
1. **Eliminated `curl | bash` Pattern** Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
1. **Eliminated `curl | bash` Pattern** How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Containerization Strategy and Architecture Constraints
This document outlines the containerization approach for the multi-agent system, addressing both security concerns and architectural constraints while maintaining functionality.
Overview
After careful analysis, we've determined that agents can be divided into two categories based on authentication and technical requirements:
- Host-Only Agents (Cannot be containerized due to authentication constraints)
- Containerizable Agents (Can run fully in Docker containers)
This division creates fundamental architectural constraints that affect how the system operates in automated workflows.
Agent Classification
Host-Only Agents
These agents MUST run on the host system due to authentication requirements:
Claude Code
- Reason: Requires machine-specific subscription authentication
- Details: Claude CLI uses browser-based OAuth flow tied to the host machine
- Documentation: See
docs/agents/claude-auth.md
Gemini CLI
- UPDATE: Now fully containerizable! See
automation/corporate-proxy/gemini/ - Container Options:
- Standard container with host auth:
tools/cli/containers/run_gemini_container.sh - Corporate proxy version:
automation/corporate-proxy/gemini/
- Standard container with host auth:
- Documentation: See
automation/corporate-proxy/gemini/README.md
Containerizable Agents
These agents can run in Docker containers with proper configuration:
Codex
- Authentication: Auth file mounted from host (
~/.codex/auth.json) - Container:
mcp-codexorcodex-agent - Requirements: Node.js runtime
- Helper Script:
tools/cli/containers/run_codex_container.sh
OpenCode
- Authentication: API key via environment variable
- Container:
openrouter-agents - Requirements: Node.js runtime
Crush (Charm Bracelet)
- Authentication: API key via config file
- Container:
openrouter-agents - Requirements: Go runtime
Architectural Constraints
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.
- 5d ago First seen · 198 lines · 0 tokens per session scan B 97542f5b3890
containerization-strategy is an agent published in the GitHub repository AndrewAltimit/template-repo (131 stars, last pushed 2mo ago), licensed Unlicense. It costs nothing until one of its globs matches a file; then it loads 1,467 tokens. A static security scan graded it B with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
devops
The DevOps agent handles everything between "it works on my machine" and "it works in production." It creates Docker configurations with multi-stage builds for minimal images, GitHub Actions workflows for automated testing and deployment, environment variable management with template files and secret handling, and…
creating-agents
Agents are created from templates or from scratch. Each agent runs as an isolated Docker container with its own filesystem, credentials, and MCP server configuration.
agent-session
Trinity has two conversation surfaces, and the difference is memory.
agent-files
Two-panel file manager in the Agent Detail Files tab for browsing, previewing, and editing agent workspace files.
agent-logs
View container logs for debugging and real-time telemetry metrics in the agent header.
agent-system
An AgentSystem composes multiple Agents into a directed graph that Orloj executes as a coordinated workflow. The graph defines how messages flow between agents during task execution.