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.
git clone --depth 1 https://github.com/wangke19/gemini-ai-helpersWrote 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/commands/wangke19/gemini-ai-helpers/cluster-node-health-check)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/cluster-node-health-check"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/cluster-node-health-check/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/commands/wangke19/gemini-ai-helpers/cluster-node-health-check"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/cluster-node-health-check.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.00020 | $0.07414 |
| Opus 5 | $0.00010 | $0.03707 |
| Sonnet 5 | $0.00004 | $0.01483 |
| Haiku 4.5 | $0.00002 | $0.00741 |
Grade A, and why
cluster-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 9d 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.
This is a copy
100% identical to cluster-node-health-check — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 761 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
node:cluster-node-health-check
Synopsis
/node:cluster-node-health-check [--node <node-name>] [--verbose] [--output-format json|text]
Description
The /node:cluster-node-health-check command performs an extensive diagnostic of Kubernetes/OpenShift cluster nodes to assess their operational health, stability, and performance. It automates the validation of node-level components including kubelet, CRI-O container runtime, system resources, and node conditions to ensure nodes are functioning as expected.
The command runs a comprehensive set of health checks covering node status, kubelet health, container runtime (CRI-O) operations, resource utilization, system daemons, and kernel parameters. It also detects degraded states, disk/memory pressure, network issues, and recent warning events.
Specifically, it performs the following:
- Detects and validates the availability of oc or kubectl CLI tools and verifies cluster connectivity.
- Checks all node statuses (Ready, MemoryPressure, DiskPressure, PIDPressure, NetworkUnavailable) and reports any abnormal conditions with detailed reasons and messages.
- Validates kubelet service health on each node, detecting service failures, high restart counts, and configuration issues.
- Performs CRI-O runtime health checks to ensure container operations are functioning correctly.
- Inspects resource utilization including CPU, memory, disk space, and process/pod counts against allocatable resources.
- Evaluates system daemon health (systemd services) critical for node operations.
- Examines kernel parameters and system tunables relevant to Kubernetes operations.
- Scans for recent warning events at the node level and for pods running on nodes.
- Reviews certificate validity for kubelet client certificates.
- Identifies node taints, labels, and scheduling constraints that may affect workload placement.
- Generates a clear, color-coded summary report and optionally exports findings in JSON format for automation or CI integration.
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.
- 9d ago First seen · 761 lines · 20 tokens per session scan A acafdf1a2f1c
cluster-node-health-check is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 20 tokens to every session and 7,414 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to cluster-node-health-check, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
audit
Run a structured codebase audit. Maps the architecture, assesses health (compliance, tests, docs), performs deep analysis (security, performance, code quality), and synthesizes a prioritized roadmap. Outputs land under docs/audit/ in this project. Phases 0-3 with human checkpoints between each phase. Use /audit-quick…
wtfp:report-bug
Collect a reproducible bug report and publish it only after explicit user approval.
fix
Diagnose and fix bugs, errors, and issues in code.
bug-report
Structured bug-fix protocol per docs/methodology/bug-protocol.md. Use when asked to '/bug-report', 'I found a bug', 'something is broken', 'fix this bug', 'report a bug', 'this is broken'.
issue:discover-by-prompt
Discover issues from user prompt with Gemini-planned iterative multi-agent exploration. Uses ACE semantic search for context gathering and supports cross-module comparison (e.g., frontend vs backend API contracts).
issue:discover
Discover potential issues from multiple perspectives (bug, UX, test, quality, security, performance, maintainability, best-practices) using CLI explore. Supports Exa external research for security and best-practices perspectives.