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-logging-pipelinegit 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-logging-pipeline)<a href="https://agentmods.dev/skills/kudig-io/kudig-database/k8s-logging-pipeline"><img src="https://agentmods.dev/badge/skills/kudig-io/kudig-database/k8s-logging-pipeline/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-logging-pipeline"><img src="https://agentmods.dev/badge/skills/kudig-io/kudig-database/k8s-logging-pipeline.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.00026 | $0.04258 |
| Opus 5.5 | $0.00010 | $0.01703 |
| Sonnet 5.5 | $0.00005 | $0.00852 |
| Haiku 4.5 | $0.00003 | $0.00426 |
Grade A, and why
k8s-logging-pipeline 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| Elasticsearch 集群健康为 red | `curl elasticsearch:9200/_cluster/health` | 0.95 | How it starts
The opening of the file, as written. The whole thing — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
生产环境安全提示
本文档包含可直接执行的运维命令。执行前请确认：当前目标集群与 Namespace 是否正确；是否具备足够的 RBAC 权限；是否已在非生产环境验证。命令风险等级标注：🔴 高风险（可能造成数据丢失或服务中断）、🟡 中风险（会修改集群状态，但通常可回滚）、🟢 低风险/只读（信息收集，无副作用）。
K8s Logging Pipeline Failure 诊断与修复
日志收集管道（[[fluentd|Fluentd]]、Fluent Bit、Filebeat 等）是 [[kubernetes|Kubernetes]] 可观测性的重要组成部分。当日志收集中断时，问题排查将失去关键线索，安全审计也会受到影响。
本 [[SKILL|Skill]] 覆盖日志代理异常、后端存储（ES/Loki）不可用、日志丢弃、解析错误等全部常见根因的诊断和修复。
何时使用此 Skill
| 症状 | 检测方法 | 置信度 |
|---|---|---|
| 日志查询返回空或旧数据 | Kibana/Grafana Explore | 0.90 |
| Fluentd/Fluent Bit Pod 异常 | kubectl get pods -n logging |
0.95 |
| Elasticsearch 集群健康为 red | curl elasticsearch:9200/_cluster/health |
0.95 |
| 日志量突然下降 | 日志系统监控面板 | 0.85 |
| Loki ingester 内存过高 | kubectl top pods -n loki |
0.85 |
排除条件: 节点磁盘满 → SKILL-NODE-001; 网络不通 → SKILL-NET-001
快速分级（2 分钟内完成）
影响范围
├── 生产日志完全中断 ────────────→ P0（15min 内修复）
├── 部分 namespace 日志缺失 ──────→ P1（30min 内修复）
├── 日志解析/字段错误 ───────────→ P2（2h 内修复）
└── 日志延迟增大 ────────────────→ P2（2h 内修复）
立即升级条件:
- 所有日志收集代理同时失败
- 日志后端（ES/Loki）集群不可用
- 合规审计日志中断
执行流程
# 🟢 低风险：只读/信息收集，通常无副作用
工单/告警触发
│
▼
┌──────────────┐ 脚本: scripts/diagnose-quick.sh
│ Phase 1 │ 内容: kubectl 快速检查（只读）
│ 快速检查 │ Step: D1.1-D1.5
└──────┬───────┘
│ 确认根因
▼
┌──────────────┐ 参考: reference/remediation-playbook.md
│ 修复操作 │ 风险: LOW → MEDIUM → HIGH
│ REM-001~005 │
└──────┬───────┘
│
▼
┌──────────────┐ 脚本: scripts/verify-logging.sh
│ 验证确认 │ 检查: 日志代理/后端/日志流
└──────────────┘
可用脚本
| 脚本 | 用途 | 参数 | 风险 |
|---|---|---|---|
scripts/diagnose-quick.sh |
日志管道快速诊断 | LOGGING_NAMESPACE |
只读 |
scripts/verify-logging.sh |
修复后验证 | LOGGING_NAMESPACE |
只读 |
根因概览 (5 种)
| RC ID | 根因 | 概率 | 首选修复 | 风险 |
|---|---|---|---|---|
| RC-001 | 日志代理（Fluentd/Fluent Bit）异常 | 高 | REM-001 重启/修复代理 | MEDIUM |
| RC-002 | 后端存储（ES/Loki）不可用 | 高 | REM-002 修复后端 | HIGH |
| RC-003 | 日志解析/过滤配置错误 | 中 | REM-003 修正配置 | LOW |
| RC-004 | 节点日志文件丢失或权限问题 | 中 | REM-004 修复节点 | MEDIUM |
| RC-005 | 日志量过大导致缓冲溢出 | 中 | REM-005 调整缓冲 | LOW |
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 8c9a97ee48bf
- 1mo ago First seen · 326 lines · 26 tokens per session scan A 47d8963cbb3c
k8s-logging-pipeline is a skill published in the GitHub repository kudig-io/kudig-database (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 26 tokens to every session and 4,258 once invoked, about $0.0001 per session on Opus 5.5. 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-31.
Other skills, from other repositories
k8s-debug
Inspect pod logs, analyze resource quotas, trace network policies, check deployment rollout status, run cluster health checks for Kubernetes. Use this skill when diagnosing Kubernetes cluster issues, debugging failing pods, investigating network connectivity problems, analyzing resource usage, troubleshooting…
kubernetes
Kubernetes operations playbook for deploying services: core objects, probes, resource sizing, safe rollouts, and fast kubectl debugging.
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.
kube-medic
Kubernetes Cluster Triage & Diagnostics — instant AI-powered incident triage via kubectl.
log-dive
Unified log search across Loki, Elasticsearch, and CloudWatch. Natural language queries translated to LogQL, ES DSL, or CloudWatch filter patterns. Read-only. Never modifies or deletes logs.
zeabur-server-ssh
Use when debugging services on a user's dedicated server via SSH. Use when needing to run a command on the server, inspect pods, check container logs, view k8s resources, or run kubectl commands. Use when "service exec" is insufficient and you need server-level access. Use when user says "check my server", "run X on…