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-policynpx skills add yindia/rootcause --skill k8s-policygit 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-policy)<a href="https://agentmods.dev/skills/yindia/rootcause/k8s-policy"><img src="https://agentmods.dev/badge/skills/yindia/rootcause/k8s-policy.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.01542 |
| Opus 5 | $0.00000 | $0.00771 |
| Sonnet 5 | $0.00000 | $0.00308 |
| Haiku 4.5 | $0.00000 | $0.00154 |
Grade A, and why
k8s-policy 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 6d 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 — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: k8s-policy
Comprehensive Kyverno policy diagnostics for admission failures, policy report analysis, and enforcement posture validation.
Trigger Phrases
Use this skill when the user mentions:
- kyverno denied request
- policy violation
- admission webhook block
- require labels policy
- require resource limits policy
- block privileged container
- policy report failed
- audit vs enforce behavior
RootCause Tools Allowed
Only use these tool names in this skill:
k8s.kyverno_detectk8s.diagnose_kyvernok8s.describek8s.listk8s.events
Kyverno Workflow Overview
Canonical path:
- detect Kyverno,
- diagnose policy and controller health,
- identify failing policy/rule,
- separate audit findings from enforce blocks,
- provide remediation with policy intent preserved.
Policy Types Reference
Validate policies
Purpose:
- enforce required fields/labels/security constraints.
Examples:
- require
ownerlabel, - require memory/cpu requests and limits,
- block privileged containers.
Mutate policies
Purpose:
- add defaults or normalize fields.
Examples:
- inject standard labels,
- default imagePullPolicy,
- enforce namespace annotations.
Generate policies
Purpose:
- create dependent resources automatically.
Examples:
- generate network policy baseline,
- generate role bindings for namespaces.
Audit vs Enforce Modes
Interpretation:
Audit: violations reported, requests allowed.Enforce: violations block admission.
When incident is active:
- first confirm if block is from
Enforcepolicy. - avoid disabling policy blindly; propose compliant manifest fix first.
Step-by-Step Investigation
Step 1: Detect Kyverno installation
Use k8s.kyverno_detect.
If not detected:
- stop Kyverno-specific diagnosis,
- report absence clearly.
Step 2: Run platform diagnosis
Use k8s.diagnose_kyverno:
namespace: kyverno
limit: 100
Collect:
- controller readiness,
- policy readiness,
- report failures,
- warning events.
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.
- 6d ago First seen · 309 lines · 0 tokens per session scan A dc91466be589
k8s-policy 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,542 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
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.
securing-helm-chart-deployments
Secure Helm chart deployments by validating chart integrity, scanning templates for misconfigurations, and enforcing security contexts in Kubernetes releases.
k8s-network-policy
Review Kubernetes NetworkPolicies — what is actually permitted to reach a workload, and whether the answer can be trusted. Use when asked what can talk to a pod, whether a namespace is restricted, why traffic is being blocked, or for any security review of cluster network segmentation.
k8s-service-path
Trace the Kubernetes service path — Service to selector to pods to EndpointSlices to readiness, plus Ingress routing. Use when a service is getting no traffic, an ingress is not routing, or someone asks why a workload is unreachable inside a cluster.