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 kudig-io/kudig-database --skill k8s-control-planegit clone --depth 1 https://github.com/kudig-io/kudig-databaseWrote 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/kudig-io/kudig-database/k8s-control-plane)<a href="https://agentmods.dev/skills/kudig-io/kudig-database/k8s-control-plane"><img src="https://agentmods.dev/badge/skills/kudig-io/kudig-database/k8s-control-plane/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/kudig-io/kudig-database/k8s-control-plane"><img src="https://agentmods.dev/badge/skills/kudig-io/kudig-database/k8s-control-plane.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.00000 | $0.07153 |
| Opus 5.5 | $0.00000 | $0.02861 |
| Sonnet 5.5 | $0.00000 | $0.01431 |
| Haiku 4.5 | $0.00000 | $0.00715 |
Grade C, and why
k8s-control-plane scanned grade C 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 1mo 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
> - `rm -rf (系统/数据路径)`：删除系统或数据文件，可能摧毁节点或丢失全部数据 How it starts
The opening of the file, as written. The whole thing — 575 lines — stays where its author put it; the contents beside it link to each section on GitHub.
生产环境安全提示
本文档包含可直接执行的运维命令。执行前请确认：当前目标集群与 Namespace 是否正确；是否具备足够的 RBAC 权限；是否已在非生产环境验证。命令风险等级标注：🔴 高风险（可能造成数据丢失或服务中断）、🟡 中风险（会修改集群状态，但通常可回滚）、🟢 低风险/只读（信息收集，无副作用）。
Control Plane Failure
概述
API [[23-实体/02-K8s核心组件/etcd.md|etcd]]/Scheduler 问题的诊断与修复 Skill。
快速诊断
./scripts/diagnose-quick.sh <namespace>
修复动作
| # | 修复动作 | 风险 |
|---|---|---|
| R1 | 检查资源配置和状态 | 低 |
| R2 | 重启相关组件 | 中 |
验证修复
./scripts/verify-control-plane.sh <namespace>
远程顾问信息收集
作为远程顾问，我无法直接连接你的集群。请帮我收集以下信息，我会根据你提供的内容给出准确的诊断建议。
第一步：快速确认（30 秒内回答）
- 影响范围：这个问题影响多少个节点 / Pod / 命名空间？
- 紧急程度：业务是否已中断？是否有用户投诉？
- 发生时间：问题是突然发生还是逐渐恶化？最近是否有变更？
第二步：关键信息（请提供你能获取的）
- kubectl 版本：
kubectl version --short的输出 - K8s 集群版本：
kubectl get nodes -o wide中的 VERSION 列 - 节点状态：控制平面节点是否正常？工作节点是否正常？
第三步：诊断信息（按需补充）
如果以下命令你无法执行，请直接告诉我「无法执行」，我会提供替代方案。
- 相关组件日志：
kubectl logs -n <namespace> <pod>的最后 30 行 - 节点资源：
kubectl top nodes或kubectl describe node <node>的 Capacity/Allocated resources - 近期变更：最近 24 小时是否有部署、扩缩容、配置变更？
如果信息不足
如果你目前只能提供部分信息，请从第一步开始。我会根据已有信息先给出初步判断，并告诉你还需要收集什么。
替代沟通方式：如果你不方便执行命令，也可以直接描述你看到的页面/告警内容，我会帮你解读。
命令替代方案
如果你无法执行以下命令，请参考对应的替代方案。
通用替代方案
| 原命令 | 无法执行的原因 | 替代方案 A | 替代方案 B |
|---|---|---|---|
kubectl get pods |
无 kubectl 权限 | 通过集群管理控制台查看 Pod 列表 | 请有权限的同事执行并截图 |
kubectl logs <pod> |
无日志权限 | 查看应用自身的日志文件（/var/log/） | 使用日志聚合系统（如 ELK/Loki）查询 |
kubectl describe node <node> |
无节点查看权限 | 查看监控系统的节点仪表盘 | 使用 kubectl get node -o yaml（如权限允许） |
ssh <node> |
无法 SSH 到节点 | 使用 kubectl debug node/<node> -it --image=busybox |
通过跳板机访问：ssh -J bastion <node> |
systemctl status kubelet |
无法进入节点 | 查看节点上的 kubelet 日志：kubectl logs -n kube-system <kubelet-pod> |
查看容器运行时日志 |
docker/crictl |
无容器运行时权限 | 使用 kubectl exec 进入容器检查 |
查看容器运行时的事件 |
如果以上都无法执行
如果你因为安全策略、网络隔离或权限限制无法执行任何诊断命令：
- 请收集你能访问的任何信息：
- 监控系统的截图
- 告警通知的内容
- 应用自身的错误页面/日志
- 最近是否有变更（部署、扩缩容、配置更新）
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed · +19 lines b49c110b7598
- 1mo ago First seen · 556 lines · 0 tokens per session scan C 00d553a315ac
k8s-control-plane is a skill published in the GitHub repository kudig-io/kudig-database (6 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 7,153 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
cluster-events
Analyze cluster-wide Kubernetes events to identify issues and patterns. Aggregates Warning events, detects high-frequency patterns, and correlates related events.
networkpolicy-debug
Diagnose NetworkPolicy-related connectivity issues (traffic unexpectedly blocked, default-deny effects, egress blocking DNS). Identifies which NetworkPolicies affect a pod, checks ingress/egress rules, and verifies CNI support.
statefulset-debug
Diagnose StatefulSet rollout and scaling failures (ordered update stuck, OnDelete not updating, partition misconfiguration, PVC binding deadlocks). Checks update strategy, pod ordinal progression, PVC bindings, and ordered startup to identify why a StatefulSet is not progressing.
ingress-debug
Diagnose Ingress failures (rules not matching, backend unreachable, TLS errors, no address assigned). Checks Ingress resources, IngressClass, backend Services, and controller health to identify why external traffic is not routed correctly.
quota-debug
Diagnose Kubernetes native ResourceQuota and LimitRange admission rejections (exceeded quota, forbidden by LimitRange, FailedCreate). Checks namespace quotas, current usage, LimitRange constraints, and ReplicaSet events to identify why pods cannot be created. Not applicable to Volcano Queue — use…
volcano-diagnose-pod
Diagnose Volcano-managed Pod scheduling issues. Checks Pod status, PodGroup, events, and Queue to identify scheduling failures.