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.
git clone --depth 1 https://github.com/pedrol-cmd/brain-drinWrote 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/pedrol-cmd/brain-drin/docker-harden)<a href="https://agentmods.dev/commands/pedrol-cmd/brain-drin/docker-harden"><img src="https://agentmods.dev/badge/commands/pedrol-cmd/brain-drin/docker-harden.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.1 | $0.00012 | $0.00082 |
| Opus 5 | $0.00006 | $0.00041 |
| Sonnet 5 | $0.00002 | $0.00016 |
| Haiku 4.5 | $0.00001 | $0.00008 |
Grade A, and why
docker-harden 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 3d 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.
What it actually says
/docker-harden
Optimizes your containerization strategy.
Usage
- Provide a Dockerfile.
- Agent applies multi-stage builds, minimal base images, and non-root users.
- Verifies image size and security scan.
Specialist Agent
@devops-engineer @security-auditor
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.
- 3d ago First seen · 17 lines · 12 tokens per session scan A 44bf11764fa6
docker-harden is a command published in the GitHub repository pedrol-cmd/brain-drin (11 stars, last pushed 4mo ago), licensed MIT. It adds 12 tokens to every session and 82 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
create-docker-mcp-tunnel
Stand up an Anthropic MCP tunnel locally with Docker Compose so Claude can call a private MCP server (manual-credentials quickstart).
cisco-isovalent-platform-setup
Install the Isovalent platform on Kubernetes (Cilium CNI, Hubble observability, Tetragon eBPF runtime security) in either OSS or Enterprise edition. Renders Helm values and install/upgrade scripts; this is the platform install prerequisite for the Splunk Observability + Splunk Platform integration done by…
build-agent
Build Docker images for Golden Armada agents.
application-crud
A command reference for creating and managing Coolify applications connected to private GitHub repositories. It covers application records, deployment settings, and common API errors.
review-helm
Run Helm chart review for structure, best practices, and K8s security/operational issues in templates.
create-operator
Guided workflow to create a complete Kubernetes CRD operator.