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-multiclustergit 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-multicluster)<a href="https://agentmods.dev/skills/rohitg00/kubectl-mcp-server/k8s-multicluster"><img src="https://agentmods.dev/badge/skills/rohitg00/kubectl-mcp-server/k8s-multicluster/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-multicluster"><img src="https://agentmods.dev/badge/skills/rohitg00/kubectl-mcp-server/k8s-multicluster.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 6 findings, 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 37 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.
- high Privilege Escalation · line 39 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.
- high Privilege Escalation · line 52 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.
- high Privilege Escalation · line 120 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.
- high Privilege Escalation · line 206 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.
- high Privilege Escalation · line 117 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.00038 | $0.01249 |
| Opus 5 | $0.00019 | $0.00624 |
| Sonnet 5 | $0.00008 | $0.00250 |
| Haiku 4.5 | $0.00004 | $0.00125 |
Grade A, and why
k8s-multicluster 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Cluster Kubernetes Management
Cross-cluster operations and context management using kubectl-mcp-server's multi-cluster support.
When to Apply
Use this skill when:
- User mentions: "cluster", "context", "multi-cluster", "cross-cluster"
- Operations: switching contexts, comparing clusters, federated deployments
- Keywords: "different environment", "production vs staging", "all clusters"
Priority Rules
| Priority | Rule | Impact | Tools |
|---|---|---|---|
| 1 | Always specify context for prod | CRITICAL | context parameter |
| 2 | List contexts before switching | HIGH | list_contexts_tool |
| 3 | Compare before promoting | MEDIUM | compare_namespaces |
| 4 | Use naming conventions | LOW | prod-*, staging-* |
Quick Reference
| Task | Tool | Example |
|---|---|---|
| List contexts | list_contexts_tool |
list_contexts_tool() |
| View kubeconfig | kubeconfig_view |
kubeconfig_view() |
| List CAPI clusters | capi_clusters_list_tool |
capi_clusters_list_tool(namespace) |
| Get CAPI kubeconfig | capi_cluster_kubeconfig_tool |
capi_cluster_kubeconfig_tool(name, namespace) |
Context Management
List Available Contexts
list_contexts_tool()
View Current Context
kubeconfig_view()
Switch Context
CLI: kubectl-mcp-server context <context-name>
Cross-Cluster Operations
All kubectl-mcp-server tools support the context parameter:
get_pods(namespace="default", context="production-cluster")
get_pods(namespace="default", context="staging-cluster")
Common Multi-Cluster Patterns
Compare Environments
compare_namespaces(
namespace1="production",
namespace2="staging",
resource_type="deployment",
context="production-cluster"
)
Parallel Queries
Query multiple clusters simultaneously:
get_pods(namespace="app", context="prod-us-east")
get_pods(namespace="app", context="prod-eu-west")
get_pods(namespace="app", context="development")
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.
- 10d ago First seen · 215 lines · 38 tokens per session scan A 228c5839a035
k8s-multicluster is a skill published in the GitHub repository rohitg00/kubectl-mcp-server (956 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 1,249 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
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.
deployment
Kubernetes Deployment 管理.
qovery-deploy
Deploys any application, database, Helm chart, Terraform module, or managed infrastructure Blueprint (RDS, Redis, S3, and more) to Kubernetes via Qovery. Analyzes the user's codebase, creates missing Dockerfiles, provisions databases (container, managed, or blueprint) and cloud resources, sets up environment…
kubernetes-operator
Deploy and manage applications on Kubernetes. Covers deployments, services, ingress, HPA, secrets, and production-grade cluster configuration.