use-k3sup

use-k3sup is a skill for Claude Code from slicervm/agent-skills. It costs 30 tokens per session (3,209 once invoked), scanned C, original, MIT.

A setup process for creating K3s clusters, which are lightweight Kubernetes clusters, with the k3sup or k3sup-pro tools. It covers local and remote virtual machines, including high-availability setups.

In plain words
What is it for?
Use it to install Kubernetes or K3s, create single-node or high-availability clusters, configure access, and run the setup on Slicer or remote VMs.
Why use it?
It provides defined procedures for installing K3s and preparing the machines and access needed to use the cluster. The exact workflow depends on whether the machines are local, remote, or part of an HA cluster.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to install Kubernetes or K3s, create single-node or high-availability clusters, configure access, and run the setup on Slicer or remote VMs.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/slicervm/agent-skills/use-k3sup
Install

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.

Any agent
npx skills add slicervm/agent-skills --skill use-k3sup
Clone the repo
git clone --depth 1 https://github.com/slicervm/agent-skills

Made for: Claude Code.

Its marketplace also offers this one on its own, as the plugin use-k3sup/plugin install use-k3sup after adding the marketplace above.

Wrote 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.

agentmods badge for use-k3sup

README.md
[![agentmods](https://agentmods.dev/badge/skills/slicervm/agent-skills/use-k3sup/github.svg)](https://agentmods.dev/skills/slicervm/agent-skills/use-k3sup)
Your own site
<a href="https://agentmods.dev/skills/slicervm/agent-skills/use-k3sup"><img src="https://agentmods.dev/badge/skills/slicervm/agent-skills/use-k3sup/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.

agentmods 80×15 button for use-k3sup

Your own site · 80×15
<a href="https://agentmods.dev/skills/slicervm/agent-skills/use-k3sup"><img src="https://agentmods.dev/badge/skills/slicervm/agent-skills/use-k3sup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,209 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe. ✓ AI security review Sonnet 5 · 6 Sept 2026 📄 Read the review
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00030 $0.03209
Opus 5 $0.00015 $0.01605
Sonnet 5 $0.00006 $0.00642
Haiku 4.5 $0.00003 $0.00321

Measured 9d ago against content hash 56f017383d98, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade C, and why

use-k3sup scanned grade C with 2 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 9d 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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

curl -SLs https://get.arkade.dev | bash

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -SLs https://get.arkade.dev | bash
skills/use-k3sup/SKILL.md · 388 lines

How it starts

The opening of the file, as written. The whole thing — 388 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Use K3sup with Slicer VMs

Use this skill when the user asks for:

  • install Kubernetes
  • install k3s / create k3s cluster
  • run k3sup or k3sup-pro
  • provision single-node K3s or HA k3s with multiple slicer VMs

For the single-node local in-VM flow (no traefik, svclb LoadBalancer, kubeconfig merged into ~/.kube/config, nginx smoke test via 127.0.0.1), see the companion use-k3s skill — it is the verified short path for "just get me a working local cluster with kubectl". This skill covers the remote (SSH) and HA (k3sup-pro) flows.

Golden rules for agent behavior

  • Prefer native Slicer commands (slicer vm exec, slicer vm shell, slicer vm cp) over SSH when the VM is local.
  • For long or interactive terminal workflows, use slicer vm shell once and keep state there.
  • Never run cluster bootstrap logic in userdata that blocks (cluster install/ready/token/join/proxy/port-forward). Use userdata for base package installs only.
  • For slicer VM workflows, prefer the normal default user shell (implicit UID) and run privileged commands with passwordless sudo; do not default to root shells (--uid 0) unless explicitly requested.
  • For single-node local installs on a slicer VM: prefer k3sup install --local from that VM.
  • For any remote install (--host / --ip), always make SSH identity explicit (--ssh-key) and run from your current host.
  • For k3sup-pro, run from a host with SSH access to the target VMs, not inside the target VM.
  • For API-launched slicer VMs that need SSH, pass identity at launch with --ssh-key using a raw public key string (from $(cat ~/.ssh/id_ed25519.pub)), or use --import-user to import keys by GitHub username.
  • On slicer-mac, do not target or reuse slicer-1 unless the user explicitly requests it.
  • On slicer-mac, any new API-launched VM must be created in the sbox host group (for example, slicer vm add sbox ...).

Tool installation strategy (preferred)

  • On the host machine (outside a VM), always install CLI tooling through arkade first:

Read the full file on GitHub · 388 lines

Changes

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.

  1. 9d ago First seen · 388 lines · 30 tokens per session scan F 56f017383d98

Subscribe to this mod's changes

use-k3sup is a skill published in the GitHub repository slicervm/agent-skills (5 stars, last pushed 3d ago), licensed MIT. It adds 30 tokens to every session and 3,209 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

gke-compute-classes

Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…

google/skills · 83 tokens

gke-workload-security

Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…

google/skills · 181 tokens

gke-reliability

Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).

google/skills · 73 tokens

nemo-automodel-launcher-config

Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.

NVIDIA/skills · 30 tokens

azure-mgmt-botservice-dotnet

Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".

microsoft/skills · 78 tokens

cloud-architect

Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…

Jeffallan/claude-skills · 71 tokens