cluster-resource-health

cluster-resource-health is a skill for Claude Code, Codex from caipe-io/ai-platform-engineering. It costs 41 tokens per session (502 once invoked), scanned A, original, Apache-2.0.

A health check for Kubernetes clusters running on Amazon EKS. Kubernetes runs containerized applications, while a cluster is the group of machines and services that run them.

In plain words
What is it for?
Use it to audit cluster health, investigate capacity problems, inspect node and pod status, review CPU and memory use, and find problematic workloads.
Why use it?
It shows failing applications, unhealthy machines, resource pressure, capacity risks, and alerts that can otherwise be spread across many systems.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to audit cluster health, investigate capacity problems, inspect node and pod status, review CPU and memory use, and find problematic workloads.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/caipe-io/ai-platform-engineering/cluster-resource-health
Install

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.

Any agent
npx skills add caipe-io/ai-platform-engineering --skill cluster-resource-health
Clone the repo
git clone --depth 1 https://github.com/caipe-io/ai-platform-engineering

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for cluster-resource-health

README.md
[![agentmods](https://agentmods.dev/badge/skills/caipe-io/ai-platform-engineering/cluster-resource-health/github.svg)](https://agentmods.dev/skills/caipe-io/ai-platform-engineering/cluster-resource-health)
Your own site
<a href="https://agentmods.dev/skills/caipe-io/ai-platform-engineering/cluster-resource-health"><img src="https://agentmods.dev/badge/skills/caipe-io/ai-platform-engineering/cluster-resource-health/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.

agentmods 80×15 button for cluster-resource-health

Your own site · 80×15
<a href="https://agentmods.dev/skills/caipe-io/ai-platform-engineering/cluster-resource-health"><img src="https://agentmods.dev/badge/skills/caipe-io/ai-platform-engineering/cluster-resource-health.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 502 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00041 $0.00502
Opus 5 $0.00020 $0.00251
Sonnet 5 $0.00008 $0.00100
Haiku 4.5 $0.00004 $0.00050

Measured 12d ago against content hash 446095b690ee, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

cluster-resource-health 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 12d 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.

charts/ai-platform-engineering/data/skills/cluster-resource-health/SKILL.md · 58 lines

What it actually says

Cluster Resource Health

Query AWS EKS clusters for node health, pod status, resource utilization, and alerts to produce a cluster health dashboard.

Instructions

Phase 1: Cluster Overview (AWS Agent)

  1. List EKS clusters and their status
  2. Check Kubernetes version - current vs. latest, end-of-support date

Phase 2: Node Health

  1. Inspect node conditions - Ready, MemoryPressure, DiskPressure, PIDPressure
  2. Resource utilization per node - CPU, Memory, Pod count

Phase 3: Pod Health

  1. Identify problematic pods - CrashLoopBackOff, ImagePullBackOff, OOMKilled, Pending
  2. Namespace-level summary - pods running, pending, failed per namespace

Phase 4: Resource Capacity Analysis

  1. Cluster-wide utilization - total CPU/Memory requested vs. allocatable
  2. Capacity risks - nodes at >80%, namespaces exceeding quotas

Output Format

```markdown

Cluster Resource Health Report

Cluster Summary

Cluster Version Nodes Status Overall Health
prod-us-west-2 1.29 12/12 Ready Active HEALTHY

Resource Utilization

Resource Requested Allocatable Utilization
CPU 38 cores 48 cores 79%
Memory 96 Gi 128 Gi 75%
```

Examples

  • "Check the health of our EKS clusters"
  • "Are there any failing pods in production?"
  • "Show me cluster resource utilization"
  • "Which nodes are under memory pressure?"

Guidelines

  • Check all clusters unless a specific cluster is requested
  • Flag any node above 85% resource utilization as a capacity risk
  • For CrashLoopBackOff pods, suggest checking logs as the immediate action
  • EKS version end-of-support should be flagged at least 90 days before EOL
  • Use kubectl read-only commands only (never modify cluster state during health checks)
Files

What ships with it

1 file 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.

Changes

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.

  1. 12d ago First seen · 58 lines · 41 tokens per session scan A 446095b690ee

Subscribe to this mod's changes

cluster-resource-health is a skill published in the GitHub repository caipe-io/ai-platform-engineering (407 stars, last pushed today), licensed Apache-2.0. It adds 41 tokens to every session and 502 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.