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 yindia/rootcause --skill k8s-ciliumgit clone --depth 1 https://github.com/yindia/rootcauseWrote 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/yindia/rootcause/k8s-cilium)<a href="https://agentmods.dev/skills/yindia/rootcause/k8s-cilium"><img src="https://agentmods.dev/badge/skills/yindia/rootcause/k8s-cilium.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.00000 | $0.01554 |
| Opus 5 | $0.00000 | $0.00777 |
| Sonnet 5 | $0.00000 | $0.00311 |
| Haiku 4.5 | $0.00000 | $0.00155 |
Grade A, and why
k8s-cilium 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 7d 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: k8s-cilium
Comprehensive Cilium diagnostics for control-plane detection, endpoint health, network policy behavior, and connectivity failures.
Includes practical CiliumNetworkPolicy examples and Hubble-centric investigation concepts.
Trigger Phrases
Use this skill when the user mentions:
- cilium issue
- cni problem
- cilium endpoint not ready
- policy denied traffic
- dropped traffic
- hubble flow gap
- pod to pod connectivity failed
- service reachable from some pods only
- egress policy blocked
RootCause Tools Allowed
Only use these tool names in this skill:
k8s.cilium_detectk8s.diagnose_ciliumk8s.describek8s.listk8s.eventsk8s.network_debug
Cilium Workflow Overview
Canonical sequence:
- detect Cilium footprint,
- diagnose Cilium health,
- inspect affected endpoints and policies,
- correlate with service-level network evidence.
Step 1: Detect Cilium Installation
Use k8s.cilium_detect first.
Outcome handling:
- detected: continue with Cilium-specific diagnosis.
- not detected: stop Cilium branch and pivot to generic network diagnostics.
Step 2: Run Cluster/Namespace Diagnosis
Use k8s.diagnose_cilium for aggregated state.
Example:
namespace: payments
limit: 100
Read for:
- endpoint health summary,
- policy status warnings,
- node-level Cilium issues,
- recurring warning events.
Step 3: Inventory Cilium Resources
Use k8s.list for policy and endpoint visibility.
Example:
namespace: payments
resources:
- kind: CiliumNetworkPolicy
- kind: CiliumEndpoint
- kind: CiliumNode
Step 4: Inspect Target Resources
Use k8s.describe in this priority order:
- failing CiliumEndpoint,
- governing CiliumNetworkPolicy,
- affected service/pod context.
Watch for:
- identity allocation errors,
- endpoint policy enforcement modes,
- selector mismatch in policies,
- stale labels after rollout.
Step 5: Correlate with Service Path
Use k8s.network_debug on affected service to validate:
- endpoint selection,
- potential policy denials,
- load balancer path effects.
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.
- 7d ago First seen · 253 lines · 0 tokens per session scan A facb6d9a5d17
k8s-cilium is a skill published in the GitHub repository yindia/rootcause (42 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,554 tokens. 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-30.
Other skills, from other repositories
helm
A guide to Helm, a package manager for Kubernetes applications. Helm uses reusable packages called Charts to install, configure, upgrade, inspect, and remove groups of Kubernetes resources.
bazel-k8s-expert
Expert knowledge for deploying Quarkus/Java applications to Kubernetes using Bazel. Covers rulesk8s, Helm, Kustomize, ConfigMaps, Secrets, and health probes.
k8s-deployer
Kubernetes deployment management - generate manifests, Helm charts, manage rollouts, check cluster status, and apply security best practices.
k8s-ingress-gateway
A troubleshooting guide for Kubernetes Ingress and Gateway configurations. Kubernetes is a system for running containers, and Ingress and Gateway components route web traffic to those containers.
kubernetes-operator
Deploy and manage applications on Kubernetes. Covers deployments, services, ingress, HPA, secrets, and production-grade cluster configuration.
hunt-k8s
Hunt Kubernetes & Docker — API anonymous access, kubelet 10250 exec (SPDY/WebSocket, NOT plain POST) and the simpler /run primitive, etcd 2379 unauth, dashboard skip-login, RBAC misconfig, secret/SA-token abuse, docker.sock host escape, runc/container-escape (Leaky Vessels CVE-2024-21626), API-server-mediated…