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 rohitg00/kubectl-mcp-server --skill k8s-diagnosticsgit clone --depth 1 https://github.com/rohitg00/kubectl-mcp-serverWrote 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/rohitg00/kubectl-mcp-server/k8s-diagnostics)<a href="https://agentmods.dev/skills/rohitg00/kubectl-mcp-server/k8s-diagnostics"><img src="https://agentmods.dev/badge/skills/rohitg00/kubectl-mcp-server/k8s-diagnostics/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/rohitg00/kubectl-mcp-server/k8s-diagnostics"><img src="https://agentmods.dev/badge/skills/rohitg00/kubectl-mcp-server/k8s-diagnostics.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 95 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00036 | $0.00737 |
| Opus 5 | $0.00018 | $0.00368 |
| Sonnet 5 | $0.00007 | $0.00147 |
| Haiku 4.5 | $0.00004 | $0.00074 |
Grade A, and why
k8s-diagnostics 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 10d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kubernetes Diagnostics
Analyze cluster health and compare resources using kubectl-mcp-server's diagnostic tools.
When to Apply
Use this skill when:
- User mentions: "metrics", "health check", "compare", "analysis", "capacity"
- Operations: cluster health assessment, environment comparison, resource analysis
- Keywords: "how much", "usage", "difference between", "capacity planning"
Priority Rules
| Priority | Rule | Impact | Tools |
|---|---|---|---|
| 1 | Check metrics-server before using metrics | CRITICAL | get_resource_metrics |
| 2 | Run health check before deployments | HIGH | cluster_health_check |
| 3 | Compare staging vs prod before release | MEDIUM | compare_namespaces |
| 4 | Document baseline metrics | LOW | get_nodes_summary |
Quick Reference
| Task | Tool | Example |
|---|---|---|
| Cluster health | cluster_health_check |
cluster_health_check() |
| Pod metrics | get_resource_metrics |
get_resource_metrics(namespace) |
| Node summary | get_nodes_summary |
get_nodes_summary() |
| Compare envs | compare_namespaces |
compare_namespaces(ns1, ns2, type) |
| List CRDs | list_crds |
list_crds() |
Resource Metrics
get_resource_metrics(namespace="default")
get_node_metrics()
get_top_pods(namespace="default", sort_by="cpu")
get_top_pods(namespace="default", sort_by="memory")
Cluster Health Check
cluster_health_check()
get_cluster_info()
Compare Environments
compare_namespaces(
namespace1="staging",
namespace2="production",
resource_type="deployment"
)
compare_namespaces(
namespace1="default",
namespace2="default",
resource_type="deployment",
context1="staging-cluster",
context2="prod-cluster"
)
API Discovery
get_api_versions()
check_crd_exists(crd_name="certificates.cert-manager.io")
list_crds()
Resource Analysis
get_nodes_summary()
kubeconfig_view()
list_contexts_tool()
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.
- 10d ago First seen · 133 lines · 36 tokens per session scan A 98e2c82cbffd
k8s-diagnostics is a skill published in the GitHub repository rohitg00/kubectl-mcp-server (956 stars, last pushed 5mo ago), licensed MIT. It adds 36 tokens to every session and 737 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
helm-expert
Expert-level Helm 3 package management, chart development, templating, and production operations. Use when the user mentions Kubernetes, package manager, charts, templates, or deployment, or when the task involves Helm Architecture, Chart Structure, Values.yaml, or Helm Hooks.
kubernetes
Kubernetes operations playbook for deploying services: core objects, probes, resource sizing, safe rollouts, and fast kubectl debugging.
kubernetes-docs
Kubernetes 1.36 — Pods, Deployments, Services, Ingress, ConfigMaps, Secrets, RBAC, CRDs, Operators, kubectl, Helm.
bazel-k8s-expert
Expert knowledge for deploying Quarkus/Java applications to Kubernetes using Bazel. Covers rulesk8s, Helm, Kustomize, ConfigMaps, Secrets, and health probes.
kubernetes-patterns
Kubernetes deployment patterns, resource configuration, and operational best practices.
deployment
Kubernetes Deployment 管理.