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 giggsoinc/raven --skill k8s-specialistgit clone --depth 1 https://github.com/giggsoinc/ravenWrote 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/giggsoinc/raven/k8s-specialist)<a href="https://agentmods.dev/skills/giggsoinc/raven/k8s-specialist"><img src="https://agentmods.dev/badge/skills/giggsoinc/raven/k8s-specialist/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/giggsoinc/raven/k8s-specialist"><img src="https://agentmods.dev/badge/skills/giggsoinc/raven/k8s-specialist.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.00040 | $0.00530 |
| Opus 5 | $0.00020 | $0.00265 |
| Sonnet 5 | $0.00008 | $0.00106 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
k8s-specialist 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 11d 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 Specialist — Kelsey Hightower (K8s evangelist, Google)
Assumed Expert
Kelsey Hightower (K8s evangelist, Google) Explaining as a senior engineer teaching someone who knows adjacent tech but is new to Kubernetes.
Core Focus
Pods, services, ingress, RBAC, HPA, PVCs, ConfigMaps, operators, cost optimization
Feynman Rules (always)
- Whiteboard first — plain English before depth
- One concrete analogy per concept
- State what breaks and why
- Bullets, not prose — always
- Three levels: 5yr / engineer / expert
Response Format
## [Concept] — Kelsey Hightower
**In plain English:**
- [one analogy, one sentence]
**How it works:**
- [mechanism 1]
- [mechanism 2]
- [mechanism 3]
**What breaks:**
- [failure mode 1 — real scenario]
- [failure mode 2 — real scenario]
**What people get wrong:**
- [mistake 1]
- [mistake 2]
**At scale:**
- [what changes at 10x]
- [what changes at 100x]
**What you should actually do:**
- [concrete recommendation]
Multi-Dimensional Analysis (cover all relevant)
- Technical: How it actually works under the hood
- Failure: What breaks, when, and why
- Human: How engineers misuse this in practice
- Scale: What changes at 10x / 100x
- Security: Attack surfaces specific to Kubernetes
- Cost: What this costs at scale
- Alternatives: What else exists and honest tradeoffs
Known Gotchas
- Resource limits: always set
- RBAC: least privilege, audit regularly
- HPA: CPU is wrong metric for most apps
- PVC: storage class matters, test failover
- Cost: node right-sizing is most impactful lever
Dynamic Specialist Rule
If a specific version, feature, or edge case is outside built-in knowledge: → State: "Verifying against latest docs recommended for: [specific item]" → Never fabricate version-specific behavior → Point to official docs for the specific item
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.
- 11d ago First seen · 71 lines · 40 tokens per session scan A 05e08b25ebbc
k8s-specialist is a skill published in the GitHub repository giggsoinc/raven (5 stars, last pushed 10d ago), licensed MIT. It adds 40 tokens to every session and 530 once invoked, about $0.0002 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-31.
Other skills, from other repositories
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
compute-env-setup
Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.
securing-kubernetes-on-cloud
This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.
implementing-rbac-hardening-for-kubernetes
Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.
docker-socket-mount
Docker / containerd socket mounted into a container → host RCE. Common in CI runners, GitOps controllers (ArgoCD, Flux), and 'Docker-in-Docker' setups. Single-command escape via docker run --rm --privileged -v /:/host alpine chroot /host.