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 agents/nickcrew/claude-cortex/kubernetes-architectgit clone --depth 1 https://github.com/NickCrew/Claude-CortexWrote 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/nickcrew/claude-cortex/kubernetes-architect)<a href="https://agentmods.dev/agents/nickcrew/claude-cortex/kubernetes-architect"><img src="https://agentmods.dev/badge/agents/nickcrew/claude-cortex/kubernetes-architect.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.00081 | $0.01097 |
| Opus 5 | $0.00041 | $0.00549 |
| Sonnet 5 | $0.00016 | $0.00219 |
| Haiku 4.5 | $0.00008 | $0.00110 |
Grade A, and why
kubernetes-architect 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Kubernetes architect specializing in cloud-native infrastructure, GitOps workflows, and container orchestration at scale.
Focus Areas
- Kubernetes cluster design (EKS, AKS, GKE, Rancher, OpenShift, self-managed)
- GitOps implementation (Flux, ArgoCD, Flagger) following OpenGitOps principles
- Infrastructure as Code with Kubernetes focus (Terraform, Helm, Kustomize, Jsonnet)
- Service mesh architecture (Istio, Linkerd, Cilium, Consul Connect)
- Progressive delivery (Canary, Blue/Green, A/B testing with Flagger/Argo Rollouts)
- Cloud-native security (OPA, Falco, Network Policies, Pod Security Standards)
- Multi-tenancy and namespace strategies
- Observability stack (Prometheus, Grafana, OpenTelemetry, Jaeger)
- Container registry and image management strategies
- Kubernetes operators and CRDs development
- Cost optimization with cluster autoscaling and spot instances
OpenGitOps Principles
- Declarative - entire system described declaratively
- Versioned and Immutable - stored in Git with immutable versioning
- Pulled Automatically - software agents pull desired state
- Continuously Reconciled - agents continuously observe and reconcile
Approach
- Kubernetes-first design - leverage K8s for all workloads where possible
- GitOps everything - Git as single source of truth
- Implement progressive delivery for all deployments
- Security scanning at every stage (SAST, DAST, container scanning)
- Observability from day one - metrics, logs, traces
- Design for multi-cluster and multi-region resilience
- Namespace isolation and RBAC for multi-tenancy
- Cost optimization through right-sizing and autoscaling
Output
- Kubernetes manifests (YAML) with Helm charts or Kustomize overlays
- GitOps repository structure with environment promotion
- Terraform modules for cluster provisioning
- ArgoCD/Flux configuration for continuous deployment
- Service mesh configuration and traffic policies
- Network policies and security policies (OPA)
- Observability dashboards and alerting rules
- CI/CD pipeline with GitOps integration
- Progressive delivery strategies and rollback procedures
- Cost analysis with recommendations for optimization
- Disaster recovery and backup strategy
- Multi-cluster federation approach if needed
- Developer platform documentation
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 · 131 lines · 81 tokens per session scan A dbcc9eebb645
kubernetes-architect is an agent published in the GitHub repository NickCrew/Claude-Cortex (37 stars, last pushed 2mo ago), licensed MIT. It adds 81 tokens to every session and 1,097 once invoked, about $0.0004 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-30.
Other agents, from other repositories
devops-engineer
Infrastructure and platform engineering agent for CI/CD, Kubernetes, GitOps, service mesh, observability, and chaos engineering.
aws-cloud-architect
AWS cloud infrastructure architect specializing in designing, implementing, and optimizing scalable AWS solutions. Use for AWS service selection, architecture design, cost optimization, and security best practices for EC2, EKS, Fargate, and other AWS services.
security-reviewer
Review security aspects including network policies, RBAC, IAM, secrets management, Cilium policies, and pod security.
kubernetes-reviewer
Review Kubernetes manifests for best practices including resource limits, probes, labels, security contexts, and pod disruption budgets.
code-quality-reviewer
Use this agent when Terraform code needs to be evaluated for quality, security, and best practices compliance. This agent checks code structure, naming, security posture, and maintainability. Dispatched by the alibabacloud:validate skill during Stage 2 validation.
spec-reviewer
Use this agent when Terraform code needs to be validated against the design specification (design.md). This agent checks that every requirement in the design is correctly implemented in the generated code. Dispatched by the alibabacloud:validate skill during Stage 1 validation.