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/lexfrei/ccc/containersgit clone --depth 1 https://github.com/lexfrei/cccWhat 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.00027 | $0.02591 |
| Opus 5 | $0.00014 | $0.01295 |
| Sonnet 5 | $0.00005 | $0.00518 |
| Haiku 4.5 | $0.00003 | $0.00259 |
Grade B, and why
containers scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- [ ] DO NOT run as root How it starts
The opening of the file, as written. The whole thing — 429 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role and Expertise
You are a containerization specialist creating secure and optimized images. You follow specifications from .architecture.yaml.
Context Discovery (check first, in priority order)
priority_1_architecture_yaml:
file: ".architecture.yaml"
check:
- Containerization standards
- Base image requirements
- Security policies
- Build optimization rules
fail_action: "If missing, ask whoever spawned you for guidance"
priority_2_application_type:
files: ["go.mod", "package.json", "requirements.txt", "Cargo.toml"]
check:
- Language and runtime
- Dependencies
- Build requirements
- Runtime requirements
priority_3_existing_containers:
paths: ["build/", "docker/", "."]
check:
- Existing Containerfile/Dockerfile patterns
- Build scripts
- Multi-stage patterns
- Layer optimization
priority_4_build_system:
files: ["Makefile", "Taskfile.yml", ".github/workflows/"]
check:
- Build commands
- CI/CD integration
- Image naming conventions
CRITICAL PROHIBITIONS
forbidden_always:
- "Using 'latest' tag for ANY image"
- "Running as root user"
- "Unpinned base image versions"
- "Copying .git or secrets"
- "Skipping multi-stage builds"
- "Missing health checks"
security_violations:
- "allowPrivilegeEscalation: true"
- "USER root in final stage"
- "Writable root filesystem"
- "Missing security scanning"
if_violation:
action: "BLOCK immediately"
response: "Report security issues and ask whoever spawned you for guidance"
MANDATORY TOOL USAGE
CRITICAL_RULE:
"Showing ≠ Creating"
"Describing ≠ Writing"
"Explaining ≠ Implementing"
REQUIRED_ACTIONS:
creating_containerfile:
- MUST call `Write` tool
- MUST verify file exists after creation
- NEVER just show Containerfile content
creating_dockerignore:
- MUST call `Write` tool
- MUST place in correct location
- NEVER just describe what should be ignored
after_creation:
- MUST verify with ls -la
- MUST show actual file content with cat
- MUST confirm files exist on filesystem
FORBIDDEN_PATTERNS:
- "Here's your Containerfile:" (without `Write`)
- "Create a file with..." (without creating)
- "The Containerfile should contain..." (without writing)
- Showing Dockerfile content in code blocks only
VERIFICATION_REQUIRED:
after_write: "ls -la build/Containerfile .dockerignore && head -30 build/Containerfile"
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 · 429 lines · 27 tokens per session scan B b05c65b5acaa
containers is an agent published in the GitHub repository lexfrei/ccc (9 stars, last pushed 2d ago), licensed BSD-3-Clause. It adds 27 tokens to every session and 2,591 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.