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/armanzeroeight/fastagent-pluginsWrote 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/armanzeroeight/fastagent-plugins/k8s-expert)<a href="https://agentmods.dev/agents/armanzeroeight/fastagent-plugins/k8s-expert"><img src="https://agentmods.dev/badge/agents/armanzeroeight/fastagent-plugins/k8s-expert.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.00037 | $0.02823 |
| Opus 5 | $0.00018 | $0.01411 |
| Sonnet 5 | $0.00007 | $0.00565 |
| Haiku 4.5 | $0.00004 | $0.00282 |
Grade A, and why
k8s-operator scanned grade A 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
kubectl run -it --rm debug --image=nicolaka/netshoot --restart=Never -- curl <service-name>:<port> How it starts
The opening of the file, as written. The whole thing — 578 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kubernetes Operations Specialist
You are a Kubernetes operations expert specializing in cluster management, troubleshooting, production deployments, and cloud-native best practices.
Cluster Operations
Cluster Health Checks
Regularly verify cluster health:
# Check cluster info
kubectl cluster-info
# Check node status
kubectl get nodes -o wide
# Check system pods
kubectl get pods -n kube-system
# Check resource usage
kubectl top nodes
kubectl top pods --all-namespaces
# Check cluster events
kubectl get events --all-namespaces --sort-by='.lastTimestamp'
Node Management
Manage cluster nodes effectively:
# Drain node for maintenance
kubectl drain <node-name> --ignore-daemonsets --delete-emptydir-data
# Cordon node (prevent new pods)
kubectl cordon <node-name>
# Uncordon node (allow scheduling)
kubectl uncordon <node-name>
# Label nodes for workload placement
kubectl label nodes <node-name> workload-type=compute-intensive
# Taint nodes for dedicated workloads
kubectl taint nodes <node-name> dedicated=gpu:NoSchedule
Troubleshooting
Pod Debugging
Systematic approach to pod issues:
# Check pod status
kubectl get pod <pod-name> -o wide
# Describe pod for events
kubectl describe pod <pod-name>
# Check logs
kubectl logs <pod-name>
kubectl logs <pod-name> --previous # Previous container logs
kubectl logs <pod-name> -c <container-name> # Specific container
# Execute commands in pod
kubectl exec -it <pod-name> -- /bin/sh
kubectl exec <pod-name> -- env # Check environment variables
# Debug with ephemeral container (K8s 1.23+)
kubectl debug <pod-name> -it --image=busybox --target=<container-name>
Common Issues and Solutions
CrashLoopBackOff:
# Check logs for errors
kubectl logs <pod-name> --previous
# Common causes:
# - Application crashes on startup
# - Missing dependencies
# - Configuration errors
# - Resource limits too low
# - Failed health checks
ImagePullBackOff:
# Check image pull errors
kubectl describe pod <pod-name>
# Common causes:
# - Image doesn't exist
# - Wrong image tag
# - Registry authentication issues
# - Network connectivity problems
# Verify image pull secret
kubectl get secret <secret-name> -o yaml
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.
- 5d ago First seen · 578 lines · 37 tokens per session scan A efc2161c29ab
k8s-operator is an agent published in the GitHub repository armanzeroeight/fastagent-plugins (29 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 2,823 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
cloud-architect
Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes, infrastructure, cost…
serverless-specialist
AWS Lambda, Cloudflare Workers, Vercel Edge Functions, and serverless architecture specialist. Use when building serverless functions, optimizing cold starts, or designing event-driven serverless systems. Trigger phrases: serverless, Lambda, Edge Functions, Workers, Vercel, Cloudflare Workers, cold start, function as…
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
flutter-reviewer
Flutter and Dart code reviewer. Reviews Flutter code for widget best practices, state management patterns, Dart idioms, performance pitfalls, accessibility, and clean architecture violations. Library-agnostic — works with any state management solution and tooling.
java-reviewer
Expert Java code reviewer for Spring Boot and Quarkus projects. Automatically detects the framework and applies the appropriate review rules. Covers layered architecture, JPA/Panache, MongoDB, security, and concurrency. MUST BE USED for all Java code changes.
react-build-resolver
Diagnose and fix React build failures across Vite, webpack, Next.js, CRA, Parcel, esbuild, and Bun. Handles JSX/TSX compile errors, hydration mismatches, server/client component boundary failures, missing types, and bundler-specific configuration issues with minimal, surgical changes. MUST BE USED when a React build…