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 initializ/forge --skill k8s-incident-triagegit clone --depth 1 https://github.com/initializ/forgeWrote 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/initializ/forge/k8s-incident-triage)<a href="https://agentmods.dev/skills/initializ/forge/k8s-incident-triage"><img src="https://agentmods.dev/badge/skills/initializ/forge/k8s-incident-triage.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 24 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.00041 | $0.01510 |
| Opus 5 | $0.00020 | $0.00755 |
| Sonnet 5 | $0.00008 | $0.00302 |
| Haiku 4.5 | $0.00004 | $0.00151 |
Grade A, and why
k8s-incident-triage 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 8d 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 — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kubernetes Incident Triage
Performs read-only triage of Kubernetes workloads and namespaces using kubectl.
Supports:
- Natural language input (human mode)
- Structured JSON input (automation mode)
This skill NEVER mutates cluster state.
Tool Usage
This skill uses cli_execute with kubectl commands exclusively.
NEVER use http_request or web_search to interact with Kubernetes.
All cluster operations MUST go through kubectl via the cli_execute tool.
Tool: k8s_triage
Diagnose unhealthy Kubernetes workloads, pods, or namespaces.
Output format: Use markdown tables for pod/workload status summaries. Wrap kubectl output and log excerpts in text code blocks. Use bash for recommended next-step commands.
Input Modes
1) Human Mode (Natural Language)
Input is a plain string.
Examples:
triage payments-prodtriage deployment payments-api in payments-prodwhy are pods pending in checkout-prod?investigate crashloop in payments-prodtriage pod api-7c9f6d7f86-abcde in payments-prodcheck rollout of deployment payments-api in prod
Behavior:
- Parse namespace, workload, pod, or selector intent.
- If namespace omitted, use
$DEFAULT_NAMESPACEif set. - If ambiguity exists, default to namespace-level triage.
- Never require the user to remember JSON fields.
2) Automation Mode (Structured JSON)
Input JSON schema:
{ "namespace": "payments-prod", "workload_kind": "deployment", "workload_name": "payments-api", "pod_name": null, "label_selector": null, "include_logs": true, "logs_tail_lines": 200, "include_previous_logs": true, "events_limit": 50, "include_node_diagnostics": true, "include_metrics": false, "output_format": "markdown" }
Rules:
namespaceis required.- If
pod_nameprovided → pod-level triage. - If workload fields provided → workload-level triage.
- Else → namespace scan.
Triage Process
Step 0 — Preconditions
Verify cluster access:
kubectl version --client kubectl cluster-info
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.
- 8d ago First seen · 322 lines · 41 tokens per session scan A bcd28d2708bc
k8s-incident-triage is a skill published in the GitHub repository initializ/forge (227 stars, last pushed yesterday), licensed Apache-2.0. It adds 41 tokens to every session and 1,510 once invoked, about $0.0002 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
Diagnose CrashLoopBackOff
Triage pods restarting repeatedly and identify the most likely root cause.
kube-medic
Kubernetes Cluster Triage & Diagnostics — instant AI-powered incident triage via kubectl.
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.