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 skills add ihatesea69/kiro-kit --skill kubernetes-opsgit clone --depth 1 https://github.com/ihatesea69/kiro-kitWrote 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/skills/ihatesea69/kiro-kit/kubernetes-ops)<a href="https://agentmods.dev/skills/ihatesea69/kiro-kit/kubernetes-ops"><img src="https://agentmods.dev/badge/skills/ihatesea69/kiro-kit/kubernetes-ops/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/skills/ihatesea69/kiro-kit/kubernetes-ops"><img src="https://agentmods.dev/badge/skills/ihatesea69/kiro-kit/kubernetes-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00350 |
| Opus 5 | $0.00014 | $0.00175 |
| Sonnet 5 | $0.00005 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
kubernetes-ops 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 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.
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.
What it actually says
Kubernetes Operations
Activate this skill when working with Kubernetes clusters and workloads.
When to Use
- Deploying applications to Kubernetes
- Troubleshooting pod failures or scheduling issues
- Configuring networking (services, ingress, network policies)
- Managing secrets and configuration
- Scaling workloads and configuring autoscaling
- Debugging container crashes or connectivity issues
Common Operations
# Check pod status and events
kubectl get pods -n <namespace>
kubectl describe pod <pod-name> -n <namespace>
kubectl logs <pod-name> -n <namespace> --previous
# Debug networking
kubectl exec -it <pod> -- nslookup <service>
kubectl get endpoints <service>
kubectl get networkpolicies
# Resource management
kubectl top pods -n <namespace>
kubectl get hpa
Troubleshooting Flow
- Check pod status (Pending, CrashLoopBackOff, ImagePullBackOff)
- Read events with
kubectl describe - Check logs (current and previous container)
- Verify resource requests vs node capacity
- Check network policies and service endpoints
- Verify secrets and configmaps are mounted correctly
Rules
- Always specify namespace explicitly
- Use labels and selectors consistently
- Set resource requests AND limits on all containers
- Implement liveness, readiness, and startup probes
- Use pod disruption budgets for critical workloads
- Never use
kubectl editin production -- use GitOps - Store manifests in version control
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 · 55 lines · 27 tokens per session scan A 5f77e645bcd3
kubernetes-ops is a skill published in the GitHub repository ihatesea69/kiro-kit (18 stars, last pushed 20d ago), licensed MIT. It adds 27 tokens to every session and 350 once invoked, about $0.0001 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 skills, from other repositories
devops
CI/CD, container orchestration, cloud architecture, monitoring, infrastructure security, and platform automation skills. Docker, Kubernetes, Terraform, GitHub Actions. Triggers on: CI/CD, Docker, Kubernetes, Terraform, deploy, monitoring, infra, GitOps, observability, SRE.
jfrog-devops
Manage JFrog Artifactory repositories, artifacts, Docker registry, build info, ML model registry (JFrog ML / AI Catalog), and Xray security scanning for DevOps and MLOps workflows. Use when user asks about JFrog, Artifactory, Xray, Curation, Frogbot, JFrog ML, AI Catalog, artifact management, "deploy artifact", Docker…
deploy-agent
You are the Deploy agent for this project. You own CI/CD, infrastructure-as-code, Docker, deploy scripts, and environment configuration.
deploy
Build, push, and deploy to AWS using Docker, ECR, and Terraform. Use when: deploying to dev/staging/prod, checking deploy status, rolling back, or running the deploy checklist.
docker
You are working with Docker. Apply these conventions.
docker-cli
Docker and Docker Compose commands for containerization. Use for building images, running containers, managing volumes, and orchestrating services.