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 G1Joshi/Agent-Skills --skill ranchergit clone --depth 1 https://github.com/G1Joshi/Agent-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/g1joshi/agent-skills/rancher)<a href="https://agentmods.dev/skills/g1joshi/agent-skills/rancher"><img src="https://agentmods.dev/badge/skills/g1joshi/agent-skills/rancher/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/g1joshi/agent-skills/rancher"><img src="https://agentmods.dev/badge/skills/g1joshi/agent-skills/rancher.svg" alt="Reviewed on agentmods" width="80" 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.00020 | $0.00333 |
| Opus 5 | $0.00010 | $0.00167 |
| Sonnet 5 | $0.00004 | $0.00067 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
rancher 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.
What it actually says
Rancher
Rancher is a complete software stack for teams adopting containers. It addresses the operational and security challenges of managing multiple Kubernetes clusters.
When to Use
- Multi-Cluster: Manage EKS, AKS, GKE, and on-prem RKE2 clusters from a single pane of glass.
- User Management: Unified Auth (SSO) across all clusters.
- Edge: Manage thousands of small K3s clusters (retail/IoT).
Core Concepts
RKE2
Rancher's Government-grade Kubernetes distribution. Secure by default, FIPS compliant.
Fleet
GitOps at scale. Deploy bundles of resources to 10,000 clusters simultaneously.
Cluster Explorer
A rich UI for interacting with Kubernetes resources (CRDs, logs, shells) without needing kubectl setup locally.
Best Practices (2025)
Do:
- Use Fleet: For managing deployments across many clusters. It's built into Rancher.
- Use RKE2/K3s: For the downstream clusters provided by Rancher.
- Centralize Auth: Hook Rancher up to your OIDC/AD provider once, and get RBAC across all clusters.
Don't:
- Don't expose Rancher UI publicly: It's the keys to the kingdom. Put it behind a VPN or strict Identity Aware Proxy.
References
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 · 45 lines · 20 tokens per session scan A f49de7713dad
rancher is a skill published in the GitHub repository G1Joshi/Agent-Skills (12 stars, last pushed 7mo ago), licensed MIT. It adds 20 tokens to every session and 333 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-09-03.
Other skills, from other repositories
k8s-manifests
When writing K8s YAML, designing Helm charts, setting resource limits, configuring probes, or reviewing pod security.
service-mesh
Implement service mesh for mTLS, traffic management, and observability — Istio and Linkerd patterns for Kubernetes.
cloud-run-basics
Manages Cloud Run services, jobs, and worker pools. Use when you need to deploy applications responding to HTTP requests (services), run event-triggered or scheduled tasks (jobs), or handle always-on pull-based background processing (worker pools).
shipping-and-launch
Prepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.
apify-actorization
Actorization converts existing software into reusable serverless applications compatible with the Apify platform. Actors are programs packaged as Docker images that accept well-defined JSON input, perform an action, and optionally produce structured JSON output.
infrastructure
A guide for cloud-native infrastructure: software and configuration used to run applications in containers and manage cloud resources. It covers Kubernetes, Helm, Kustomize, GitOps tools such as ArgoCD and Flux, and infrastructure-as-code tools such as Terraform and Pulumi.