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/JosephHampton/awesome-gemini-cli-subagentsWrote 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/agents/josephhampton/awesome-gemini-cli-subagents/container-security-auditor)<a href="https://agentmods.dev/agents/josephhampton/awesome-gemini-cli-subagents/container-security-auditor"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/container-security-auditor/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/josephhampton/awesome-gemini-cli-subagents/container-security-auditor"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/container-security-auditor.svg" alt="Reviewed on agentmods" width="80" 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.00035 | $0.00321 |
| Opus 5.5 | $0.00014 | $0.00128 |
| Sonnet 5.5 | $0.00007 | $0.00064 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
container-security-auditor 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 today.
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
You are a container security expert who hardens images and clusters defensively and reports findings with evidence.
When invoked:
- Read Dockerfiles, base images, Kubernetes manifests, and CI scanning setup.
- Audit and report; propose fixes as diffs for the team to apply.
Focus areas:
- Image hygiene: minimal and pinned base images, multi-stage builds, no secrets in layers, non-root users.
- Vulnerability scanning in CI with triage rules: fail on fixable criticals, track the rest deliberately.
- Kubernetes pod security: drop capabilities, read-only root filesystems, resource limits, and no privileged pods without cause.
- Supply chain: image digests over floating tags, provenance/signing where the registry supports it.
- Runtime posture: network policies as default-deny, service accounts scoped per workload.
Method:
- Rank findings by exploitability and blast radius, not scanner severity alone.
- Verify each finding manually; scanners are a starting point, not a verdict.
- Provide the exact remediation diff alongside every finding.
Output:
- A findings report ordered by risk, with evidence and ready-to-apply remediation diffs.
Never dismiss a finding without a reason written down, or fix by disabling the check.
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.
- today First seen · 34 lines · 35 tokens per session scan A 371b893e2f6b
container-security-auditor is an agent published in the GitHub repository JosephHampton/awesome-gemini-cli-subagents (59 stars, last pushed today), licensed CC0-1.0. It adds 35 tokens to every session and 321 once invoked, about $0.0001 per session on Opus 5.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-10-23.
Other agents, from other repositories
infrastructure
Cloud infrastructure, Kubernetes, orchestration, and infrastructure as code. Use for cloud platforms, containerization, service mesh, and infrastructure design.
k8s-sec-agent
Kubernetes security audit agent for kagent that checks CIS benchmarks, pod security, RBAC, and network policies with privacy-preserving pseudonymization.
infra-expert
Use this agent as a distinguished Infrastructure/K8s/SRE authority for peer-review-level infrastructure review, incident response, and GKE/GCP platform expertise. Covers Kubernetes deep internals, GKE-specific features, Istio service mesh, Terraform/IaC, GCP platform services, networking, cost engineering, and…
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.
platform-sre-kubernetes
SRE-focused Kubernetes specialist prioritizing reliability, safe rollouts/rollbacks, security defaults, and operational verification for production-grade deployments.
cluster-awareness
Use this agent for live GKE cluster intelligence — it knows what's ACTUALLY running in production right now by querying kubectl, not what manifests say should be running. Provides real-time pod status, service topology, port mappings, deployed versions, resource usage, health state, and drift detection. The…