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 agentmods add skills/yindia/rootcause/k8s-networkingnpx skills add yindia/rootcause --skill k8s-networkinggit 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-networking)<a href="https://agentmods.dev/skills/yindia/rootcause/k8s-networking"><img src="https://agentmods.dev/badge/skills/yindia/rootcause/k8s-networking.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 | $0.00000 | $0.02296 |
| Opus 5 | $0.00000 | $0.01148 |
| Sonnet 5 | $0.00000 | $0.00459 |
| Haiku 4.5 | $0.00000 | $0.00230 |
Grade A, and why
k8s-networking 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.
- pod can curl ip but not service How it starts
The opening of the file, as written. The whole thing — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: k8s-networking
Comprehensive Kubernetes networking diagnostics for service reachability, DNS, NetworkPolicy, Ingress and load balancer health, private endpoint connectivity, and evidence-driven traffic flow analysis.
Scope
Use this skill when investigating any request that includes connectivity uncertainty between clients, Ingress, Services, pods, or external dependencies.
This skill is optimized for root cause investigations, not broad architecture redesign.
Trigger Phrases
Use this skill when the user mentions:
- service unreachable
- ingress 502 or 503
- timeout or connection refused
- dns failure or nxdomain
- endpoint not found
- network policy blocked
- load balancer pending
- private link issues
- cross-namespace traffic denied
- pod can curl ip but not service
- intermittent traffic drops
- health checks failing
RootCause Tools Allowed
Only use these tool names in this skill:
k8s.network_debugk8s.private_link_debugk8s.graphk8s.describek8s.listk8s.eventsk8s.exec
Investigation Strategy
Follow a strict top-down path:
- Confirm object existence and shape.
- Validate service-to-pod wiring.
- Validate traffic policy constraints.
- Validate DNS from inside cluster.
- Validate external path and private connectivity.
- Build graph evidence and timeline summary.
Do not jump to fixes before evidence from at least two tools agrees.
Fast Triage Matrix
| Symptom | First Tool | Why |
|---|---|---|
| Service name resolves but requests timeout | k8s.network_debug |
Fast check for endpoints and policy blocks |
| Ingress returns 404/502/503 | k8s.graph |
Identifies broken edge between ingress and backend |
| Internal pod cannot resolve service FQDN | k8s.exec |
DNS proof from same runtime network context |
| Traffic denied after policy deploy | k8s.network_debug |
Policy decision visibility |
| NLB/ALB health checks failing | k8s.network_debug |
Service and LB wiring health |
| VPC endpoint/private path failing | k8s.private_link_debug |
Endpoint-side evidence for private connectivity |
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 · 326 lines · 0 tokens per session scan A badfdf3b30d2
k8s-networking 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 2,296 tokens. 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-08-30.
Other skills, from other repositories
bazel-k8s-expert
Expert knowledge for deploying Quarkus/Java applications to Kubernetes using Bazel. Covers rulesk8s, Helm, Kustomize, ConfigMaps, Secrets, and health probes.
kubernetes-review
Kubernetes & Cloud-Native Review: Reviews Kubernetes manifests, Helm charts, and cloud-native configurations for security, reliability, resource management, and best practices. Covers pods, deployments, services, ingress, RBAC, network policies, HPA, PDB, security contexts, and GitOps patterns. Use when the user…
kubernetes-operator
Deploy and manage applications on Kubernetes. Covers deployments, services, ingress, HPA, secrets, and production-grade cluster configuration.
upgrade-cluster
Use when upgrading or hardening an existing kube-hetzner cluster, including module version bumps, provider lockfile refreshes, k3s/RKE2 channel/version upgrades, immutable node replacement, system-upgrade-controller changes, or live cluster rollout validation.
securing-helm-chart-deployments
Secure Helm chart deployments by validating chart integrity, scanning templates for misconfigurations, and enforcing security contexts in Kubernetes releases.
dependabot-batch
Use when reviewing Radar's weekly Dependabot PRs and replacing the safe, 72-hour-soaked updates with one changelog-vetted, tested PR.