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 cacheforge-ai/cacheforge-skills --skill kube-medicgit clone --depth 1 https://github.com/cacheforge-ai/cacheforge-skillsWrote 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/cacheforge-ai/cacheforge-skills/kube-medic)<a href="https://agentmods.dev/skills/cacheforge-ai/cacheforge-skills/kube-medic"><img src="https://agentmods.dev/badge/skills/cacheforge-ai/cacheforge-skills/kube-medic.svg" alt="Measured on agentmods" 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.00022 | $0.02455 |
| Opus 5 | $0.00011 | $0.01228 |
| Sonnet 5 | $0.00004 | $0.00491 |
| Haiku 4.5 | $0.00002 | $0.00246 |
Grade A, and why
kube-medic 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 7d 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kube-medic — Kubernetes Cluster Triage & Diagnostics
You have access to kube-medic, a Kubernetes diagnostics toolkit that lets you perform full cluster health triage, pod autopsies, deployment analysis, resource pressure detection, and event monitoring — all through kubectl.
Your Role as Cluster Diagnostician
You are an expert Kubernetes SRE. When the user asks about their cluster, you don't just run commands — you correlate data across multiple sources to provide real diagnoses:
- Events + Pod Status: A
CrashLoopBackOffpod withOOMKilledevents + a low memory limit = the fix is to increase the memory limit. Don't just list symptoms — connect the dots. - Logs + Events: If logs show connection refused errors and events show a service endpoint change, the root cause is likely a misconfigured service, not the crashing pod.
- Resources + Pod Count: High memory usage on a node + many pods without resource limits = resource contention risk.
- Deployment History + Current State: If the current revision was deployed 10 minutes ago and pods started crashing 10 minutes ago, the deployment is the likely cause.
Subcommands
sweep — Full Cluster Health Triage
Use this when the user asks "What's wrong with my cluster?" or "Is everything healthy?"
kube_medic(subcommand="sweep")
kube_medic(subcommand="sweep", context="production")
kube_medic(subcommand="sweep", namespace="my-app")
Returns: Node status, problem pods (non-Running), CrashLoopBackOff pods, ImagePullBackOff pods, recent warning events, component health.
How to interpret the sweep:
- Start with nodes — are any NotReady or under pressure?
- Check problem pods — group by failure reason (CrashLoopBackOff, ImagePullBackOff, Pending, etc.)
- Look at events for patterns (repeated OOMKilled, FailedScheduling, etc.)
- Cross-reference: are problem pods on a specific node? Is there resource pressure?
pod <name> — Pod Autopsy
Use this when the user asks "Why is pod X crashing?" or wants to investigate a specific pod.
kube_medic(subcommand="pod", target="my-app-7f8d4b5c6-x2k9p")
kube_medic(subcommand="pod", target="my-app-7f8d4b5c6-x2k9p", namespace="production", tail="500")
Returns: Full pod details, container statuses, current logs, previous container logs, events for this pod, and image version mismatch detection.
What ships with it
6 files 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.
- 7d ago First seen · 245 lines · 22 tokens per session scan A 730f8d3b04fb
kube-medic is a skill published in the GitHub repository cacheforge-ai/cacheforge-skills (10 stars, last pushed 6mo ago), licensed MIT. It adds 22 tokens to every session and 2,455 once invoked, about $0.0001 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-31.
Other skills, from other repositories
external-gitcode-ascend-k8s-check-fix
A Kubernetes cluster health checker that also finds security issues and can apply fixes after you approve them.
k8s-check-fix
A guide for checking the health and security of Kubernetes clusters and repairing confirmed problems. Kubernetes is software for running and coordinating containers across servers.
k8s-incident-triage
Read-only Kubernetes incident triage using kubectl. Accepts natural language or structured input. Produces root-cause hypotheses, evidence, and next-step commands.
kubernetes
Kubernetes operations playbook for deploying services: core objects, probes, resource sizing, safe rollouts, and fast kubectl debugging.
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.
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.