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 scitix/siclaw --skill node-health-checkgit clone --depth 1 https://github.com/scitix/siclawWrote 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/scitix/siclaw/node-health-check)<a href="https://agentmods.dev/skills/scitix/siclaw/node-health-check"><img src="https://agentmods.dev/badge/skills/scitix/siclaw/node-health-check.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00038 | $0.01541 |
| Opus 5 | $0.00019 | $0.00771 |
| Sonnet 5 | $0.00008 | $0.00308 |
| Haiku 4.5 | $0.00004 | $0.00154 |
Grade A, and why
node-health-check 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Node Health Check
When nodes are NotReady, experiencing resource pressure, or suspected of causing pod failures, follow this flow to diagnose node-level issues.
Scope: This skill is for diagnosis only. Once you identify the root cause, report it to the user and stop. Do NOT attempt to drain, cordon, or restart nodes — that should be left to the user or cluster administrator.
Diagnostic Flow
1. Get node overview
kubectl get nodes -o wide
Note the STATUS of each node. Healthy nodes show Ready. Look for NotReady, SchedulingDisabled, or condition-related flags like Ready,SchedulingDisabled.
2. Inspect specific node conditions
For any node showing issues — one call per node:
k8s_inspect(kind: "node", name: "<node>")
This returns the node's conditions, taints, cordon state and allocatable capacity together with its
recent events and the phase distribution of the pods scheduled on it — the last of which would
otherwise be a separate kubectl get pods --field-selector spec.nodeName=… call.
Read the final status: line: partial (pods: …) means the distribution is missing, so an
absent pod count is not evidence that the node is empty.
Reach for kubectl describe node <node> when you need the Allocated resources table (what the
scheduled pods have requested, as opposed to what the node offers) or the node's labels verbatim.
Key conditions:
| Condition | Healthy Value | Problem Value | Meaning |
|---|---|---|---|
| Ready | True | False/Unknown | Kubelet is healthy and can accept pods |
| MemoryPressure | False | True | Node memory usage is critically high |
| DiskPressure | False | True | Node disk usage exceeds eviction threshold |
| PIDPressure | False | True | Too many processes running on node |
| NetworkUnavailable | False | True | Node network is not configured correctly |
Also check:
- Allocatable vs Capacity — shows total resources and what's available for pods
- Allocated resources section — shows how much is requested/limited by pods on this node
- Events — look for recent warnings
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 · 177 lines · 38 tokens per session scan A c62503472d9a
node-health-check is a skill published in the GitHub repository scitix/siclaw (233 stars, last pushed today), licensed Apache-2.0. It adds 38 tokens to every session and 1,541 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
k8s-dns-failure
A guide for diagnosing and fixing DNS problems in Kubernetes, a system for running containerised applications. It focuses on CoreDNS, the component that helps services find one another and reach external services.
incident-triage
Use when asked to triage, investigate, or diagnose a Kubernetes incident, outage, or unhealthy workload. Gives the step-by-step order of investigation and the format for the findings.
ariadne-kubernetes-graph
Use for Ariadne MCP-backed Kubernetes state questions: translate operational questions into Cypher, repair graphquery failures, and decide when graphschema or graphhealth is needed. Best for live or snapshot-backed graph data about resource relationships; do not use for codebase-only tasks or generic Kubernetes…
k8s-service-connectivity
A troubleshooting guide for Kubernetes service connectivity, where services provide stable network access to groups of running containers. It focuses on missing endpoints, selector mismatches, network policies, and kube-proxy problems.
k8s-deployment-rollout
A troubleshooting workflow for failed Kubernetes Deployment releases and rolling updates that become stuck. Kubernetes is a system for running and managing containers.
k8s-pod-crashloop
A troubleshooting guide for Kubernetes pods that repeatedly restart or run out of memory. Kubernetes is a system for running and managing containers, and a pod is its basic unit for running an application.