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 caipe-io/ai-platform-engineering --skill cluster-resource-healthgit clone --depth 1 https://github.com/caipe-io/ai-platform-engineeringWrote 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/caipe-io/ai-platform-engineering/cluster-resource-health)<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.
<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>- 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.00041 | $0.00502 |
| Opus 5.5 | $0.00016 | $0.00201 |
| Sonnet 5.5 | $0.00008 | $0.00100 |
| Haiku 4.5 | $0.00004 | $0.00050 |
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 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.
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)
- List EKS clusters and their status
- Check Kubernetes version - current vs. latest, end-of-support date
Phase 2: Node Health
- Inspect node conditions - Ready, MemoryPressure, DiskPressure, PIDPressure
- Resource utilization per node - CPU, Memory, Pod count
Phase 3: Pod Health
- Identify problematic pods - CrashLoopBackOff, ImagePullBackOff, OOMKilled, Pending
- Namespace-level summary - pods running, pending, failed per namespace
Phase 4: Resource Capacity Analysis
- Cluster-wide utilization - total CPU/Memory requested vs. allocatable
- 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)
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.
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 First seen · 58 lines · 41 tokens per session scan A 446095b690ee
cluster-resource-health is a skill published in the GitHub repository caipe-io/ai-platform-engineering (432 stars, last pushed yesterday), licensed Apache-2.0. It adds 41 tokens to every session and 502 once invoked, about $0.0002 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-30.
Other skills, from other repositories
multi-service-orchestration
PM2 process management, backend/frontend cascade execution, parallel worktree builds, and cross-service integration testing.
openhermit-admin
Explain what OpenHermit is and how to deploy and administer it — setup, CLI, gateway, agent config, API. Use when the user asks about installing, operating, or administering an OpenHermit deployment. For how agents behave for their owners/users/guests, see openhermit-guide.
diagram-architecture
Dark-themed SVG architecture/cloud/infra diagrams as HTML.
software-design-system-design
Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions "system design", "scale this", "high availability", "rate limiter", "design a URL shortener", "system design interview", "capacity planning", or "distributed…
software-design-lifecycle-deploy-ops-methodology
Use when an architect must run the deployment-and-operations handoff stage, preserve the full lifecycle-stage doctrine for deploy/ops, and turn completed design into physical topology, rollout, operations, monitoring, emergency, and rehearsal deliverables.
software-design-lifecycle-deploy-ops-deployment-arch-diagramming
A method for creating and reviewing deployment or physical architecture diagrams that show where a system runs, its network and deployment boundaries, and assumptions needed for operations.