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 seed-forge/harness-ai-kit --skill diag-k8s-pod-crashloopgit clone --depth 1 https://github.com/seed-forge/harness-ai-kitWrote 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/seed-forge/harness-ai-kit/diag-k8s-pod-crashloop)<a href="https://agentmods.dev/skills/seed-forge/harness-ai-kit/diag-k8s-pod-crashloop"><img src="https://agentmods.dev/badge/skills/seed-forge/harness-ai-kit/diag-k8s-pod-crashloop/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/seed-forge/harness-ai-kit/diag-k8s-pod-crashloop"><img src="https://agentmods.dev/badge/skills/seed-forge/harness-ai-kit/diag-k8s-pod-crashloop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 17 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 132 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00063 | $0.01199 |
| Opus 5 | $0.00032 | $0.00600 |
| Sonnet 5 | $0.00013 | $0.00240 |
| Haiku 4.5 | $0.00006 | $0.00120 |
Grade A, and why
diag-k8s-pod-crashloop 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 11d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
K8s Pod CrashLoopBackOff Full-Chain Diagnostics
用途
当 Pod 反复重启、状态显示 CrashLoopBackOff 或 Error 时触发。本技能是自包含诊断 Runbook。
输入
- kubectl 上下文（kubeconfig）
- 目标 Pod 名称 + Namespace
输出
- CrashLoop 根因分析报告 + 修复建议
诊断步骤
Step 1: Pod 状态与事件
kubectl get pod {pod_name} -n {namespace} -o wide
kubectl describe pod {pod_name} -n {namespace}
# 关注 Events 区块：OOMKilled / Error / ImagePullBackOff / FailedMount
Step 2: 容器日志
# 当前容器日志（可能在 crash 后已清空）
kubectl logs {pod_name} -n {namespace} --all-containers=true --tail=100
# 上一次崩溃的日志
kubectl logs {pod_name} -n {namespace} --all-containers=true --previous --tail=200
Step 3: 重启原因分类
| 事件关键词 | 根因 | 典型修复 |
|---|---|---|
OOMKilled |
内存超限 | 增大 resources.limits.memory 或修复内存泄漏 |
Error (exit code 1) |
应用启动失败 | 检查日志、配置、依赖服务连通性 |
ImagePullBackOff |
镜像拉取失败 | 检查 image tag、imagePullSecrets、registry 可达 |
FailedMount |
ConfigMap/Secret/PVC 挂载失败 | 检查引用是否存在 |
Liveness probe failed |
健康检查超时 | 调整 initialDelaySeconds / timeoutSeconds |
CreateContainerConfigError |
env/configMapKeyRef 缺失 | 检查引用的 ConfigMap/Secret key |
BackOff restarting |
重启间隔递增 | 以上任一原因的持续重试 |
Step 4: 资源限制与请求
kubectl get pod {pod_name} -n {namespace} -o jsonpath='{range .spec.containers[*]}{.name}: requests={.resources.requests} limits={.resources.limits}{"\n"}{end}'
Step 5: 依赖检查
# ConfigMap/Secret 是否存在
kubectl get configmap -n {namespace} | grep {configmap_name}
kubectl get secret -n {namespace} | grep {secret_name}
# PVC 状态
kubectl get pvc -n {namespace} | grep {pvc_name}
# Service 端点
kubectl get endpoints {service_name} -n {namespace}
输出模板
K8s Pod CrashLoop Analysis Report
════════════════════════════════════════
Cluster: {context}
Namespace: {namespace}
Pod: {pod_name}
Node: {node_name}
Time: {timestamp}
Pod Status
Phase: {phase}
Restart Count: {restart_count}
Last State: {last_state} (exit code: {exit_code})
Reason: {reason}
Events (last 10)
{event_1}
{event_2}
...
Container Logs (previous crash, last 20 lines)
{log_lines}
Root Cause: {root_cause}
Recommendations
1. {fix_1}
2. {fix_2}
What ships with it
3 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.
- 11d ago First seen · 147 lines · 63 tokens per session scan A 7abf3e165fe2
diag-k8s-pod-crashloop is a skill published in the GitHub repository seed-forge/harness-ai-kit (22 stars, last pushed 11d ago), licensed Apache-2.0. It adds 63 tokens to every session and 1,199 once invoked, about $0.0003 per session on Opus 5. 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
kubectl
Execute kubectl commands to manage Kubernetes clusters — query pods and deployments, deploy applications, debug containers with logs and exec, update configurations, and monitor cluster health. Use when working with Kubernetes, asking for pod status, container logs, deployment updates, cluster diagnostics, or any…
kubernetes-specialist
Use when deploying or managing Kubernetes workloads. Invoke to create deployment manifests, configure pod security policies, set up service accounts, define network isolation rules, debug pod crashes, analyze resource limits, inspect container logs, or right-size workloads. Use for Helm charts, RBAC policies…
offensive-container-escape
Container escape and breakout techniques targeting Docker, containerd, and Podman runtimes. Covers privileged container breakout via host filesystem mount and nsenter, Docker socket abuse through /var/run/docker.sock, Linux capability exploitation including CAPSYSADMIN, CAPSYSPTRACE, and CAPNETADMIN, cgroup v1…
ecs
AWS ECS container orchestration for running Docker containers. Use when deploying containerized applications, configuring task definitions, setting up services, managing clusters, or troubleshooting container issues.
eks
AWS EKS Kubernetes management for clusters, node groups, and workloads. Use when creating clusters, configuring IRSA, managing node groups, deploying applications, or integrating with AWS services.
dokploy-deploy
This skill should be used when user asks to "deploy with Dokploy", "use Dokploy Cloud", "manage self-hosted Dokploy", "deploy Docker Compose on Dokploy", "manage Dokploy databases", "configure Dokploy domains", or "look up Dokploy CLI commands".