agentmods.dev

beitlab_home_lab_cluster: Skill for Cursor

.cursor/skills/homelab-getting-started/SKILL.md

homelab-getting-started is a skill for Cursor from AndresJejen/beitlab_home_lab_cluster. It costs 72 tokens per session (630 once invoked), scanned B, original, MIT.

A setup guide for installing a homelab Kubernetes cluster on one computer, one small board such as a Raspberry Pi, or several small devices. A homelab is a personal server environment, and k3s is a lightweight version of Kubernetes for running containers.

In plain words
What is it for?
Use it to set up a single-node or multi-node homelab with uv, Ansible, the homelab command-line tool, and k3s, then retrieve the cluster configuration and check its nodes.
Why use it?
It gives newcomers a defined order for preparing the repository, configuring machines, checking access, and starting the cluster without putting real network details in version control.

Skill for Cursor

Written for Cursor: installed under .cursor/. Also seen: mentions AGENTS.md.

This is AndresJejen/beitlab_home_lab_cluster's own configuration. It tells Cursor how to work on beitlab_home_lab_cluster itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything beitlab_home_lab_cluster configures →

not rated 5repo +1 11d ago B scan 72 tokens original MIT
View source ↗ AndresJejen/beitlab_home_lab_cluster
Reuse

Borrowing it

Nothing to install: this file belongs to AndresJejen/beitlab_home_lab_cluster. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/AndresJejen/beitlab_home_lab_cluster/master/.cursor/skills/homelab-getting-started/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/AndresJejen/beitlab_home_lab_cluster

Made for: Cursor.

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 homelab-getting-started

README.md
[![agentmods](https://agentmods.dev/badge/skills/andresjejen/beitlab_home_lab_cluster/homelab-getting-started/github.svg)](https://agentmods.dev/skills/andresjejen/beitlab_home_lab_cluster/homelab-getting-started)
Your own site
<a href="https://agentmods.dev/skills/andresjejen/beitlab_home_lab_cluster/homelab-getting-started"><img src="https://agentmods.dev/badge/skills/andresjejen/beitlab_home_lab_cluster/homelab-getting-started/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 homelab-getting-started

Your own site · 80×15
<a href="https://agentmods.dev/skills/andresjejen/beitlab_home_lab_cluster/homelab-getting-started"><img src="https://agentmods.dev/badge/skills/andresjejen/beitlab_home_lab_cluster/homelab-getting-started.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 630 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00072 $0.00630
Opus 5 $0.00036 $0.00315
Sonnet 5 $0.00014 $0.00126
Haiku 4.5 $0.00007 $0.00063

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

Security

Grade B, and why

homelab-getting-started scanned grade B 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 11d 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

5. `uv run homelab ping` (add `-K` if sudo needs a password).

Makes network callslowCapability

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

they have it — do not install uv with a curl pipe unless they ask.
.cursor/skills/homelab-getting-started/SKILL.md · 56 lines

What it actually says

Homelab getting started

Read first

  • AGENTS.md
  • docs/getting-started-single-node.md when they have one machine
  • docs/getting-started.md when they have a controller plus workers
  • docs/cli.md

Do not invent a second installer. Use uv and the homelab CLI.

Workflow

  1. Confirm they cloned this repo as the workspace root.
  2. Check for uv (uv --version). If missing, point at https://docs.astral.sh/uv/getting-started/installation/ and stop until they have it — do not install uv with a curl pipe unless they ask.
  3. From the repo root: uv sync.
  4. If inventory.ini is missing:
    • one PC / one board → uv run homelab setup --profile single
    • multi-node → uv run homelab setup --profile cluster Then stop and tell them to edit hostnames, ansible_host, and ansible_user. Never write real IPs from chat into Git.
  5. uv run homelab ping (add -K if sudo needs a password).
  6. Only after ping succeeds: uv run homelab bootstrap.
  7. uv run homelab kubeconfig and kubectl get nodes -o wide.

Rules

  • inventory.ini is gitignored. Never git add it.
  • Placeholders stay lab.example, controller, 192.168.1.10.
  • Empty [workers] is valid for single-node.
  • homelab.local/node-pool=pi is the default pool label on x86 too.
  • Longhorn on one node needs k8s/longhorn/values-single-node.yaml.
  • Do not run shutdown or node-remove without an explicit confirm in the same user message.
  • Do not delete PVCs or Longhorn volumes unless they ask to destroy data.
  • After kubeconfig exists, point them at docs/secrets-off-cluster.md so passwords are not only on the server disk. Prefer uv run homelab backup-secrets when they have AWS; otherwise 1Password / GCP / Azure from that doc. Never paste secret values into chat.

If ping fails

Diagnose SSH (ssh user@host), ansible_user, and host keys. Do not disable host_key_checking globally. Ask them to accept the host key once.

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. 11d ago First seen · 56 lines · 72 tokens per session scan B 623889176bf8

Subscribe to this mod's changes

homelab-getting-started is a skill published in the GitHub repository AndresJejen/beitlab_home_lab_cluster (5 stars, last pushed 11d ago), licensed MIT. It adds 72 tokens to every session and 630 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

ContainersDevOps and cloudHardware and IoT
Related

Other skills, from other repositories

holoscan-install-container

Install Holoscan SDK via the NGC Docker container. Use for container-based installs; not for native apt/pip/Conda installs.

NVIDIA/skills · 35 tokens

doca-urom-svc

Operate the DOCA UROM Service container on BlueField Arm for remote memory operations (puts, gets, atomics, collectives) enqueued by a paired host using doca-urom: pull the NGC image, choose the UCX component, size queues, configure Comch pairing, and align host and service versions. SECURITY: the service has no…

NVIDIA/skills · 153 tokens

hsb-setup

Clone the latest NVIDIA Holoscan Sensor Bridge repo, ask which supported devkit is being used, configure the host per platform, build the correct demo container, run it, and verify HSB connectivity by pinging 192.168.0.2. Use for Holoscan Sensor Bridge setup, build, container launch, and first-connectivity bring-up.

NVIDIA/skills · 78 tokens

holoscan-install-source

Build Holoscan SDK from source via the in-tree ./run script. Use only when published packages don't meet the user's needs.

NVIDIA/skills · 32 tokens

xpu-container-run

Launch a Docker container with Intel GPU access on Linux. Encodes the correct combination of --device /dev/dri, render-group access, --ipc=host, ZEAFFINITYMASK pinning, Hugging Face cache mount, and --entrypoint /bin/bash for interactive use. Use when running any Intel-XPU container (vLLM-XPU, sglang-xpu, torch-XPU…

intel/gpu-ai-skills · 146 tokens

together-kueue

Install and use the Kueue job-queueing controller on a Together AI Kubernetes GPU cluster to gate jobs on quota. Covers installing Kueue, defining ResourceFlavor, ClusterQueue, and LocalQueue quota, submitting jobs to a queue, and watching quota admit or suspend them. Reach for it when a Together cluster's GPU pool…

togethercomputer/skills · 124 tokens