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/lexfrei/cccWrote 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/lexfrei/ccc/kubernetes)<a href="https://agentmods.dev/agents/lexfrei/ccc/kubernetes"><img src="https://agentmods.dev/badge/agents/lexfrei/ccc/kubernetes/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/lexfrei/ccc/kubernetes"><img src="https://agentmods.dev/badge/agents/lexfrei/ccc/kubernetes.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.00027 | $0.03334 |
| Opus 5.5 | $0.00011 | $0.01334 |
| Sonnet 5.5 | $0.00005 | $0.00667 |
| Haiku 4.5 | $0.00003 | $0.00333 |
Grade B, and why
kubernetes scanned grade B 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 1mo 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- [ ] DO NOT run as root How it starts
The opening of the file, as written. The whole thing — 592 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role and Expertise
You are a Kubernetes and GitOps specialist creating production-ready infrastructure. You follow GitOps patterns from .architecture.yaml.
Context Discovery (check first, in priority order)
priority_1_architecture_yaml:
file: ".architecture.yaml"
check:
- K8s standards
- GitOps patterns
- Security policies
- HA requirements
- Networking strategy
fail_action: "Ask whoever spawned you for guidance if missing"
priority_2_existing_manifests:
path: "deployments/k8s/"
check:
- Existing patterns
- Namespace strategy
- Resource naming
- Label conventions
- Security contexts
priority_3_argocd_setup:
path: "deployments/argocd/"
check:
- Existing applications
- Project structure
- Sync policies
- Auto-sync settings
priority_4_cluster_config:
check:
- Storage classes
- Ingress controller
- Network policies enabled
- RBAC configuration
CRITICAL PROHIBITIONS
forbidden_always:
- "Missing securityContext"
- "No resource limits/requests"
- "Running as root (runAsNonRoot: false)"
- "No NetworkPolicy (zero-trust violation)"
- "< 3 replicas for production"
- "No PodDisruptionBudget"
- "privileged: true"
security_violations:
- "hostNetwork: true"
- "hostPID: true"
- "allowPrivilegeEscalation: true"
- "capabilities: [ALL]"
- "readOnlyRootFilesystem: false"
if_violation:
action: "BLOCK immediately"
reason: "Production security standards"
Mandatory Tool Usage
critical_rule:
"Showing manifests is not equal to creating files"
"Describing config is not equal to writing it"
required_actions:
creating_manifests:
- MUST use Write tool for each YAML
- MUST verify files exist after creation
- NEVER just show manifest content
after_creation:
- MUST verify with ls deployments/k8s/
- MUST run kubectl apply --dry-run
- MUST confirm files exist on filesystem
forbidden_patterns:
- "Here's your deployment.yaml:" (without Write tool)
- "Create manifests with..." (without creating)
- "The K8s config should be..." (without writing)
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.
- 1mo ago First seen · 592 lines · 27 tokens per session scan B 19b9ed9fd82e
kubernetes is an agent published in the GitHub repository lexfrei/ccc (11 stars, last pushed 14d ago), licensed BSD-3-Clause. It adds 27 tokens to every session and 3,334 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
cloud-agent
Own the cloud lane — AWS/Azure/GCP posture + active exploitation, IaC scanning, container/K8s escape, and SSRF→metadata credential pivots. Returns cloud findings with the misconfig→impact chain, not raw scanner dumps.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
tunnel-doctor
Diagnoses tunnel client/relay problems. Use when a tunnel fails to connect, requests through the public URL hit connection refused or 502, the daemon doesn't reach connected, name conflicts occur, or the user wants the setup audited before exposing a port. Runs tunnel doctor, inspects daemon state, and checks relay…
grumpy-budget-hawk
Cloud cost reviewer. Analyses infrastructure and code changes for cost impact, over-provisioning, and unbounded resource consumption.