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/nomarj/sigil/kubernetes-architectgit clone --depth 1 https://github.com/NOMARJ/sigilWrote 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/nomarj/sigil/kubernetes-architect)<a href="https://agentmods.dev/agents/nomarj/sigil/kubernetes-architect"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/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.1 | $0.00083 | $0.00849 |
| Opus 5 | $0.00042 | $0.00425 |
| Sonnet 5 | $0.00017 | $0.00170 |
| Haiku 4.5 | $0.00008 | $0.00085 |
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 2d 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 — 74 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.
- 2d ago First seen · 74 lines · 83 tokens per session scan A 1ecf261ef3f8
kubernetes-architect is an agent published in the GitHub repository NOMARJ/sigil (5 stars, last pushed today), licensed Apache-2.0. It adds 83 tokens to every session and 849 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-09-03.
Other agents, from other repositories
mcp-deployment-orchestrator
Deploys MCP servers to production with containerization, Kubernetes deployments, autoscaling, monitoring, and high-availability operations. Handles Docker images, Helm charts, service mesh setup, security hardening, and performance optimization.
ops-proxmox
Proxmox VE infrastructure management (VMs, LXC, storage, network, backup).
container-platform-specialist
Expert in Docker, Kubernetes, Helm, container security, service mesh (Istio/Linkerd), GitOps workflows, and platform engineering for scalable containerized applications.
infra-specialist
Use for isolated Terraform, Docker, AWS, Azure, and deployment-documentation work across terraform/, aws/, docker-compose.yml, DEPLOYMENT.md, and agenticai/deployments/.
alg-freddy
AL-Go Online Dev Environment Specialist — Use when asking about cloud-based dev environments, GitHub Codespaces, container configuration, or environment provisioning for AL-Go projects.
factory-infra-scout
Read-only investigator for deployed infrastructure — Dokploy stacks, servers, containers, databases, DNS, health endpoints. Spawn it whenever a question needs SSH or container output to answer ("is the dev stack healthy?", "what is env var X on the deployed app?", "did the deploy pick up the new image?", "why is smoke…