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/loacher-solution/bc-agent-plugin/bc-containernpx skills add loacher-solution/bc-agent-plugin --skill bc-containergit clone --depth 1 https://github.com/loacher-solution/bc-agent-pluginWrote 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/loacher-solution/bc-agent-plugin/bc-container)<a href="https://agentmods.dev/skills/loacher-solution/bc-agent-plugin/bc-container"><img src="https://agentmods.dev/badge/skills/loacher-solution/bc-agent-plugin/bc-container.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.00051 | $0.00846 |
| Opus 5 | $0.00026 | $0.00423 |
| Sonnet 5 | $0.00010 | $0.00169 |
| Haiku 4.5 | $0.00005 | $0.00085 |
Grade A, and why
bc-container 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 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.
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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bc-container
Wraps BcContainerHelper's container lifecycle with project-aware defaults. The agent uses this skill when a task actually needs a running BC server.
When to use
- The user asks to create / set up / spin up a container.
- The user asks to run tests, and
.bc-agent/container.jsondoes not exist. - The user asks to publish and debug, and there is no container yet.
- The user asks to remove / clean up the container.
Do NOT use this skill for:
- Compile-only work → that needs symbols, and
al_downloadsymbolsviaalmcphandles that with no container. - Symbol lookup → use the
bc-symbolsMCP server.
Creating a container
1. Verify Docker Desktop
pwsh -NoProfile -File <plugin>/skills/bc-container/scripts/verify-docker.ps1
If status is not-running or not-installed, surface the message and stop.
2. Read the target version from app.json
pwsh -NoProfile -File <plugin>/skills/bc-container/scripts/read-bc-version.ps1 -AppJsonPath "<project>/app.json"
If status is missing-versions, ask the user for the platform/application version and offer to write them into app.json.
3. Create the container
Propose a container name (default: the project folder name) and ask the user to confirm. Then:
pwsh -NoProfile -File <plugin>/skills/bc-container/scripts/new-container.ps1 `
-ProjectRoot "<abs-project-root>" `
-ContainerName "<name>" `
-Platform "<from-step-2>" `
-Application "<from-step-2>"
This generates a random admin password, stores it in %LOCALAPPDATA%\bc-agent-plugin\containers\<name>.json with restricted ACLs, resolves the artifact URL, and calls New-BcContainer with -accept_eula -includeAL -includeTestToolkit.
4. Copy Test Toolkit symbols into .alpackages/
pwsh -NoProfile -File <plugin>/skills/bc-container/scripts/copy-test-toolkit-symbols.ps1 -ProjectRoot "<abs>" -ContainerName "<name>"
This gives the compiler visibility into the Test Runner / Library Assert / etc. symbols that al_downloadsymbols (global sources) cannot provide.
What ships with it
5 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 · 92 lines · 51 tokens per session scan A d71a154379d7
bc-container is a skill published in the GitHub repository loacher-solution/bc-agent-plugin (2 stars, last pushed 4mo ago), licensed MIT. It adds 51 tokens to every session and 846 once invoked, about $0.0003 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-31.
Other skills, from other repositories
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
compute-env-setup
Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.
securing-kubernetes-on-cloud
This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.
implementing-rbac-hardening-for-kubernetes
Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.
docker-socket-mount
Docker / containerd socket mounted into a container → host RCE. Common in CI runners, GitOps controllers (ArgoCD, Flux), and 'Docker-in-Docker' setups. Single-command escape via docker run --rm --privileged -v /:/host alpine chroot /host.