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 agentmods add skills/dryvist/claude-code-plugins/proxmox-cluster-opsnpx skills add dryvist/claude-code-plugins --skill proxmox-cluster-opsgit clone --depth 1 https://github.com/dryvist/claude-code-pluginsWrote 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/dryvist/claude-code-plugins/proxmox-cluster-ops)<a href="https://agentmods.dev/skills/dryvist/claude-code-plugins/proxmox-cluster-ops"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/proxmox-cluster-ops.svg" alt="Measured on agentmods" 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 | $0.00089 | $0.01211 |
| Opus 5 | $0.00044 | $0.00606 |
| Sonnet 5 | $0.00018 | $0.00242 |
| Haiku 4.5 | $0.00009 | $0.00121 |
Grade A, and why
proxmox-cluster-ops scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sk -H "Authorization: PVEAPIToken=$PVE_API_TOKEN" \ How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Proxmox VE cluster operations
Three recurring operator tasks on a Proxmox VE cluster, generalized from real bring-up and maintenance work. Every identifier is a placeholder — substitute your own node names, VMIDs, and domain.
Read-only inspection — never converge a guest by hand
Inspecting cluster or guest state (is a service active, what does a log say, is a container running) is safe to do directly. Changing anything on a live guest by hand is not — config changes belong in configuration management (Ansible or equivalent), and shape changes (new guest, resized disk) belong in infrastructure-as-code (Terraform/OpenTofu or equivalent). A manual fix that seems to need a hand-edit is a gap in that automation to close, not a thing to do live.
ssh root@<node-ip> 'pvecm status' # cluster quorum
ssh root@<node-ip> 'qm list' 'pct list' # VMs / containers on a node
ssh root@<node-ip> 'pvesh get /nodes/<node>/storage' # structured API query
Or over HTTPS with an API token, no SSH hop at all:
curl -sk -H "Authorization: PVEAPIToken=$PVE_API_TOKEN" \
"https://<node-ip>:8006/api2/json/nodes/<node>/storage" | jq .
pct exec vs a direct guest SSH — use pct exec <vmid> -- <cmd> from
the node when the guest is an LXC container and either its own SSH isn't
reachable or you only need a one-off command. Use a direct SSH to the guest
when you need an interactive shell for extended inspection, or the guest is
a VM (pct exec is container-only; use qm guest exec or SSH for VMs).
Node addresses that predate DNS bootstrapping (the Proxmox nodes themselves, before anything else can resolve) are the one legitimate place to look up a current IP from your own inventory rather than relying on a name — everything else should be addressed by FQDN.
Rolling updates that respect quorum
A cluster needs a strict majority of nodes online to stay quorate (e.g. 2 of 3, 3 of 5). Update one node at a time, and never take a second node down while the first is still rebooting or rejoining — that's the exact window where a second failure loses quorum and makes the cluster read-only.
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.
- yesterday First seen · 97 lines · 89 tokens per session scan A c58196305011
proxmox-cluster-ops is a skill published in the GitHub repository dryvist/claude-code-plugins (3 stars, last pushed today), licensed Apache-2.0. It adds 89 tokens to every session and 1,211 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.
Other skills, from other repositories
docker-deploy
Use this skill when building, containerizing, or deploying WrongStack with Docker. Triggers: user says "docker", "container", "dockerfile", "image", "docker-compose", "deploy", "containerize", "registry", "multi-stage", "distroless".
kubernetes-specialist
Use when managing Kubernetes clusters, debugging Pods and workloads, designing Helm charts, reviewing manifests, or improving deployment, scaling, and observability practices.
kubernetes
Diagnose and fix Kubernetes pods, services, networking, storage, and rollout failures with kubectl. Safety-first, read-only by default.
container-orchestration
Docker, Kubernetes, and AWS ECS/Fargate patterns. Triggers on: Dockerfile, docker-compose, kubernetes, k8s, helm, pod, deployment, service, ingress, container, image, ecs, fargate, task definition, ecs service, awsvpc, FARGATESPOT, ALB, ecs vs kubernetes.
hosting-deployment-release
Use this capability for hosting decisions, platform selection, container deployment, serverless deployment, domains, DNS, TLS, staging/production environments, blue-green, canary, rolling deploys, migrations during deploy, health checks, smoke tests, and rollback plans.
infra-deploy
Cal.com self-hosted deployment to GCP Cloud Run with Supabase PostgreSQL. Docker Compose for local dev.