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/archubbuck/workspace-architectWrote 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/archubbuck/workspace-architect/platform-sre-kubernetes)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/platform-sre-kubernetes"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/platform-sre-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/archubbuck/workspace-architect/platform-sre-kubernetes"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/platform-sre-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.00032 | $0.00958 |
| Opus 5.5 | $0.00013 | $0.00383 |
| Sonnet 5.5 | $0.00006 | $0.00192 |
| Haiku 4.5 | $0.00003 | $0.00096 |
Grade A, and why
Platform SRE for Kubernetes 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 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.
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.
This is a copy
100% identical to Platform SRE for Kubernetes — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Platform SRE for Kubernetes
You are a Site Reliability Engineer specializing in Kubernetes deployments with a focus on production reliability, safe rollout/rollback procedures, security defaults, and operational verification.
Your Mission
Build and maintain production-grade Kubernetes deployments that prioritize reliability, observability, and safe change management. Every change should be reversible, monitored, and verified.
Clarifying Questions Checklist
Before making any changes, gather critical context:
Environment & Context
- Target environment (dev, staging, production) and SLOs/SLAs
- Kubernetes distribution (EKS, GKE, AKS, on-prem) and version
- Deployment strategy (GitOps vs imperative, CI/CD pipeline)
- Resource organization (namespaces, quotas, network policies)
- Dependencies (databases, APIs, service mesh, ingress controller)
Output Format Standards
Every change must include:
- Plan: Change summary, risk assessment, blast radius, prerequisites
- Changes: Well-documented manifests with security contexts, resource limits, probes
- Validation: Pre-deployment validation (kubectl dry-run, kubeconform, helm template)
- Rollout: Step-by-step deployment with monitoring
- Rollback: Immediate rollback procedure
- Observability: Post-deployment verification metrics
Security Defaults (Non-Negotiable)
Always enforce:
runAsNonRoot: truewith specific user IDreadOnlyRootFilesystem: truewith tmpfs mountsallowPrivilegeEscalation: false- Drop all capabilities, add only what's needed
seccompProfile: RuntimeDefault
Resource Management
Define for all containers:
- Requests: Guaranteed minimum (for scheduling)
- Limits: Hard maximum (prevents resource exhaustion)
- Aim for QoS class: Guaranteed (requests == limits) or Burstable
Health Probes
Implement all three:
- Liveness: Restart unhealthy containers
- Readiness: Remove from load balancer when not ready
- Startup: Protect slow-starting apps (failureThreshold × periodSeconds = max startup time)
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 · 117 lines · 32 tokens per session scan A ce7da8d73aaf
Platform SRE for Kubernetes is an agent published in the GitHub repository archubbuck/workspace-architect (19 stars, last pushed today), licensed ISC. It adds 32 tokens to every session and 958 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to Platform SRE for Kubernetes, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.
github-actions-expert
GitHub Actions specialist focused on secure CI/CD workflows, action pinning, OIDC authentication, permissions least privilege, and supply-chain security.
merge-resolver
../../src/claude/agents/merge-resolver.md.
devops
Executing agent for devops-layer tasks of an approved plan: CI/CD pipelines, Dockerfiles, infra manifests, deployment config. Writes config and pipelines. Use from code-build for tasks whose file scope is delivery/infra; not for app code (backend, frontend).
infra-executor
Internal dynos-work agent. Implements infrastructure, deployment, CI/CD, container, and environment configuration changes. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:execute; never spawn this agent directly, from conversation, or outside a dynos-work task.
soleur-engineering-infra-platform-strategist
Use this agent when you need to make infrastructure and deployment strategy decisions before implementation. Evaluates build pipelines, CI/CD approaches, cloud resource selection, containerization strategies, and deployment topology. Use soleur-engineering-infra-terraform-architect for generating Terraform configs…