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-image-pullgit 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-image-pull)<a href="https://agentmods.dev/skills/kudig-io/kudig-database/k8s-image-pull"><img src="https://agentmods.dev/badge/skills/kudig-io/kudig-database/k8s-image-pull/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-image-pull"><img src="https://agentmods.dev/badge/skills/kudig-io/kudig-database/k8s-image-pull.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.00022 | $0.04079 |
| Opus 5.5 | $0.00009 | $0.01632 |
| Sonnet 5.5 | $0.00004 | $0.00816 |
| Haiku 4.5 | $0.00002 | $0.00408 |
Grade A, and why
k8s-image-pull 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 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.
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.
This is a copy
88% identical to k8s-config-secret — 138 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
生产环境安全提示
本文档包含可直接执行的运维命令。执行前请确认：当前目标集群与 Namespace 是否正确；是否具备足够的 RBAC 权限；是否已在非生产环境验证。命令风险等级标注：🔴 高风险（可能造成数据丢失或服务中断）、🟡 中风险（会修改集群状态，但通常可回滚）、🟢 低风险/只读（信息收集，无副作用）。
K8s Image Pull Failure 诊断与修复
ImagePullBackOff 和 ErrImagePull 是 [[kubernetes|Kubernetes]] 中最常见的 Pod 启动失败原因之一。根因可能涉及镜像不存在、标签错误、仓库认证、网络问题或节点磁盘空间不足等。
本 [[SKILL|Skill]] 覆盖全部常见镜像拉取失败根因的诊断和修复。
何时使用此 Skill
| 症状 | 检测方法 | 置信度 |
|---|---|---|
| Pod 状态为 ImagePullBackOff | `kubectl get [[Pods | pods]]` |
| Pod 状态为 ErrImagePull | kubectl get pods |
0.99 |
| Events 显示 pull access denied | kubectl describe pod Events |
0.95 |
| Events 显示 manifest unknown | kubectl describe pod Events |
0.95 |
| Pod Init:ImagePullBackOff | kubectl get pods |
0.95 |
排除条件: 网络不通 → SKILL-NET-001; 节点磁盘满 → SKILL-NODE-001
快速分级（2 分钟内完成）
影响范围
├── 核心服务全部 Pod 无法启动 ──→ P0（15min 内修复）
├── 新发布版本镜像问题 ─────────→ P1（30min 内修复）
├── 部分 Pod 镜像问题 ───────────→ P2（2h 内修复）
└── 测试环境镜像问题 ───────────→ P3（4h 内处理）
立即升级条件:
- 生产环境所有副本 ImagePullBackOff
- 镜像仓库完全不可用
- 私有仓库凭证被误删除
执行流程
# 🟢 低风险：只读/信息收集，通常无副作用
工单/告警触发
│
▼
┌──────────────┐ 脚本: scripts/diagnose-quick.sh
│ Phase 1 │ 内容: kubectl 快速检查（只读）
│ 快速检查 │ Step: D1.1-D1.6
└──────┬───────┘
│ 确认根因
▼
┌──────────────┐ 参考: reference/remediation-playbook.md
│ 修复操作 │ 风险: LOW → MEDIUM → HIGH
│ REM-001~006 │
└──────┬───────┘
│
▼
┌──────────────┐ 脚本: scripts/verify-image.sh
│ 验证确认 │ 检查: Pod 状态/镜像/事件
└──────────────┘
可用脚本
| 脚本 | 用途 | 参数 | 风险 |
|---|---|---|---|
scripts/diagnose-quick.sh |
kubectl 快速诊断 | NAMESPACE POD_NAME |
只读 |
scripts/verify-image.sh |
修复后验证 | NAMESPACE POD_NAME |
只读 |
根因概览 (6 种)
| RC ID | 根因 | 概率 | 首选修复 | 风险 |
|---|---|---|---|---|
| RC-001 | 镜像标签不存在或拼写错误 | 高 | REM-001 修正镜像 | LOW |
| RC-002 | 私有仓库认证失败 | 高 | REM-002 更新 [[secrets|secrets]] | LOW |
| RC-003 | 镜像仓库网络不可达 | 中 | REM-003 检查网络 | MEDIUM |
| RC-004 | 节点磁盘空间不足 | 中 | REM-004 清理磁盘 | LOW |
| RC-005 | 镜像平台不兼容（ARM/x86） | 低 | REM-005 修正镜像 | LOW |
| RC-006 | Rate limit / 仓库限流 | 中 | REM-006 等待/切换 | MEDIUM |
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 0027df464503
- 1mo ago First seen · 304 lines · 22 tokens per session scan A ab63b2de13cf
k8s-image-pull is a skill published in the GitHub repository kudig-io/kudig-database (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 22 tokens to every session and 4,079 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to k8s-config-secret, differing in 138 lines, and is treated as a copy.
Other skills, from other repositories
pod-management
A Kubernetes troubleshooting skill for managing Pods, the small units that run containers in Kubernetes. It covers checking Pod status, reading logs, and running commands inside containers.
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.
image-pull-debug
Diagnose container image pull failures (ErrImagePull / ImagePullBackOff). Checks pod status, containerd logs, and events to identify root cause.
pod-pending-debug
Diagnose pod scheduling failures (Pending, Unschedulable). Checks events, node resources, taints, affinity, and PVC bindings to identify why a pod cannot be scheduled.
deployment-rollout-debug
Diagnose Deployment rollout failures (stuck rollouts, ProgressDeadlineExceeded, replica mismatch). Checks rollout status, ReplicaSets, and new pod health to identify why an update is failing.