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/xobotyi/cc-foundry/containersnpx skills add xobotyi/cc-foundry --skill containersgit clone --depth 1 https://github.com/xobotyi/cc-foundryWrote 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/xobotyi/cc-foundry/containers)<a href="https://agentmods.dev/skills/xobotyi/cc-foundry/containers"><img src="https://agentmods.dev/badge/skills/xobotyi/cc-foundry/containers.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.00088 | $0.03626 |
| Opus 5 | $0.00044 | $0.01813 |
| Sonnet 5 | $0.00018 | $0.00725 |
| Haiku 4.5 | $0.00009 | $0.00363 |
Grade A, and why
containers scanned grade A 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Use appropriate check commands.** `curl -f` for HTTP services, `pg_isready` for Postgres, `redis-cli ping` for How it starts
The opening of the file, as written. The whole thing — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Containers
Security is not optional. Every container runs non-root, with dropped capabilities, on a minimal base image. Convenience defaults that weaken security posture are bugs, not trade-offs.
Security Rules
These are non-negotiable defaults for every container configuration. Apply unconditionally — no exceptions for development, convenience, or "temporary" setups.
- Run as non-root. Add a
USERinstruction with explicit UID/GID. Never run production containers as root. - Drop all capabilities.
--cap-drop=ALL, then add back only what the application genuinely requires. Most applications need zero. - Enable no-new-privileges.
--security-opt=no-new-privilegesprevents setuid/setgid escalation. - Use read-only filesystem.
--read-onlywithtmpfsmounts for/tmp,/run, and any directories the app writes to. - Never pass secrets via ENV. Visible in
docker inspect, logs, and child processes. Use mounted secret files or Docker secrets. - Scan images before deployment. Use Docker Scout, Trivy, or Grype in CI. Block images with critical CVEs.
- Use distroless for production when possible. No shell means no shell-based attacks and dramatically fewer CVEs.
- Never use
--privileged. It removes almost all security restrictions. If a workload claims to need it, decompose the requirement into specific capabilities. - Never mount the Docker socket (
/var/run/docker.sock) into containers. It grants root-equivalent control over the host. Use purpose-built APIs or socket proxies with restricted access. - Use
--initor tini/dumb-init for PID 1. Regular applications don't reap zombie processes or handle signals correctly as PID 1. Usedocker run --init,RunInit=truein Quadlets, or install tini in the Dockerfile. Without this,docker stopwaits for the kill timeout and zombies accumulate. - Verify supply chain integrity. Pin images to digest, generate SBOMs (Syft, Docker Scout), sign images with cosign/Sigstore. Use VEX documents to distinguish exploitable from non-exploitable CVEs. Block unsigned images in CI.
What ships with it
7 files 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.
- 4d ago First seen · 221 lines · 88 tokens per session scan A 5ba81fdb3c35
containers is a skill published in the GitHub repository xobotyi/cc-foundry (20 stars, last pushed yesterday), licensed MIT. It adds 88 tokens to every session and 3,626 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…