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-monitoring-alertinggit 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-monitoring-alerting)<a href="https://agentmods.dev/skills/kudig-io/kudig-database/k8s-monitoring-alerting"><img src="https://agentmods.dev/badge/skills/kudig-io/kudig-database/k8s-monitoring-alerting/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-monitoring-alerting"><img src="https://agentmods.dev/badge/skills/kudig-io/kudig-database/k8s-monitoring-alerting.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.04396 |
| Opus 5.5 | $0.00010 | $0.01758 |
| Sonnet 5.5 | $0.00005 | $0.00879 |
| Haiku 4.5 | $0.00003 | $0.00440 |
Grade A, and why
k8s-monitoring-alerting 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.
How it starts
The opening of the file, as written. The whole thing — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
生产环境安全提示
本文档包含可直接执行的运维命令。执行前请确认：当前目标集群与 Namespace 是否正确；是否具备足够的 RBAC 权限；是否已在非生产环境验证。命令风险等级标注：🔴 高风险（可能造成数据丢失或服务中断）、🟡 中风险（会修改集群状态，但通常可回滚）、🟢 低风险/只读（信息收集，无副作用）。
K8s Monitoring & Alerting Failure 诊断与修复
[[prometheus|Prometheus]]、Grafana 和 Alertmanager 是 [[kubernetes|Kubernetes]] 可观测性栈的核心。当监控异常时，可能导致问题发现延迟、告警漏报，使 SRE 团队处于"盲飞"状态。
本 [[SKILL|Skill]] 覆盖 Prometheus 采集失败、Grafana 数据源异常、Alertmanager 不发送通知、规则配置错误等全部常见根因的诊断和修复。
何时使用此 Skill
| 症状 | 检测方法 | 置信度 |
|---|---|---|
| Prometheus target 显示 DOWN | Prometheus UI / kubectl get servicemonitor |
0.95 |
| Grafana 面板无数据 | Grafana UI | 0.90 |
| Alertmanager 不发送通知 | 测试告警 | 0.85 |
| Prometheus Pod OOMKilled | kubectl get pods -n monitoring |
0.90 |
| Rule evaluation errors | Prometheus logs | 0.85 |
排除条件: 节点资源压力 → SKILL-NODE-001; 网络不通 → SKILL-NET-001
快速分级（2 分钟内完成）
影响范围
├── 生产监控完全不可用 ──────────→ P0（15min 内修复）
├── 部分指标缺失或告警漏报 ──────→ P1（30min 内修复）
├── Grafana 面板异常 ────────────→ P2（2h 内修复）
└── 非关键告警规则问题 ──────────→ P3（4h 内处理）
立即升级条件:
- 所有生产监控和告警同时中断
- Prometheus 数据持久化损坏
- 安全事件导致监控数据被篡改
执行流程
# 🟢 低风险：只读/信息收集，通常无副作用
工单/告警触发
│
▼
┌──────────────┐ 脚本: scripts/diagnose-quick.sh
│ Phase 1 │ 内容: kubectl + promql 快速检查（只读）
│ 快速检查 │ Step: D1.1-D1.5
└──────┬───────┘
│ 确认根因
▼
┌──────────────┐ 参考: reference/remediation-playbook.md
│ 修复操作 │ 风险: LOW → MEDIUM → HIGH
│ REM-001~006 │
└──────┬───────┘
│
▼
┌──────────────┐ 脚本: scripts/verify-monitoring.sh
│ 验证确认 │ 检查: Prometheus/Grafana/Alertmanager
└──────────────┘
可用脚本
| 脚本 | 用途 | 参数 | 风险 |
|---|---|---|---|
scripts/diagnose-quick.sh |
监控告警快速诊断 | MONITORING_NAMESPACE |
只读 |
scripts/verify-monitoring.sh |
修复后验证 | MONITORING_NAMESPACE |
只读 |
根因概览 (6 种)
| RC ID | 根因 | 概率 | 首选修复 | 风险 |
|---|---|---|---|---|
| RC-001 | Prometheus 存储满或 OOM | 高 | REM-001 扩容/清理 | MEDIUM |
| RC-002 | ServiceMonitor/PodMonitor 选择器错误 | 高 | REM-002 修正选择器 | LOW |
| RC-003 | Grafana 数据源配置错误 | 中 | REM-003 修正数据源 | LOW |
| RC-004 | Alertmanager 路由/接收器配置错误 | 中 | REM-004 修正配置 | LOW |
| RC-005 | 告警规则语法错误 | 中 | REM-005 修正规则 | LOW |
| RC-006 | 网络策略阻止抓取 | 低 | 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 136e4bacf7f6
- 1mo ago First seen · 331 lines · 26 tokens per session scan A 996f07729939
k8s-monitoring-alerting 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,396 once invoked, about $0.0001 per session on Opus 5.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-31.
Other skills, from other repositories
Observability with Prometheus & Grafana
Production-grade observability stack with Prometheus metrics, Grafana dashboards, PromQL query language, alerting rules, and AI-powered anomaly detection for modern cloud-native applications.
monitoring-expert
Expert-level monitoring and observability with Prometheus, Grafana, logging, and alerting. Use when the user mentions observability, Prometheus, Grafana, logging, metrics, or alerting, or when the task involves The Three Pillars of Observability, Monitoring Fundamentals, Prometheus Configuration, or Alert Rules.
monitoring-logging
Application monitoring, logging systems, and alerting.
prom-query
Prometheus Metrics Query & Alert Interpreter — query metrics, interpret timeseries, triage alerts.
monitoring-alerting-commerce
Track store health in real time with dashboards for checkout success rate, payment failures, cart errors, and custom SLO alerting.
prometheus-expert
Expert-level Prometheus monitoring, metrics collection, PromQL queries, alerting, and production operations. Use when the user mentions monitoring, metrics, observability, alerting, or PromQL, or when the task involves Prometheus Architecture, Installation on Kubernetes, ServiceMonitor, or PromQL Queries.