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 basher83/lunar-claude --skill proxmox-infrastructuregit clone --depth 1 https://github.com/basher83/lunar-claudeWrote 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/basher83/lunar-claude/proxmox-infrastructure)<a href="https://agentmods.dev/skills/basher83/lunar-claude/proxmox-infrastructure"><img src="https://agentmods.dev/badge/skills/basher83/lunar-claude/proxmox-infrastructure/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/basher83/lunar-claude/proxmox-infrastructure"><img src="https://agentmods.dev/badge/skills/basher83/lunar-claude/proxmox-infrastructure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00084 | $0.00865 |
| Opus 5 | $0.00042 | $0.00432 |
| Sonnet 5 | $0.00017 | $0.00173 |
| Haiku 4.5 | $0.00008 | $0.00086 |
Grade A, and why
proxmox-infrastructure 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Proxmox Infrastructure: Matrix/Virgo-Core Cluster
Manage 3-node Proxmox VE cluster with CEPH storage, VLAN networking, and cloud-init automation.
Available Tools
Python Scripts (uv-based)
- validate_template.py - Validate template health via Proxmox API
- cluster_status.py - Cluster health metrics and node status
- check_ceph_health.py - CEPH storage pool health monitoring
- check_cluster_health.py - Comprehensive cluster diagnostics
All scripts support --help for usage. Run with: uv run tools/<script>.py
Automation Examples
- Ansible playbooks - Template creation, VLAN bridging setup
- Terraform modules - VM cloning, multi-node deployments with dual NICs
See examples/ and workflows/ for working configurations.
Core Capabilities
Template Management:
- Ubuntu/Debian cloud-init templates with virtio-scsi
- Serial console configuration for cloud images
- Proper boot order and cloud-init CD-ROM (ide2)
Network Infrastructure:
- vmbr0: Management (VLAN 9 for Corosync)
- vmbr1: CEPH Public (192.168.5.0/24, MTU 9000)
- vmbr2: CEPH Private (192.168.7.0/24, MTU 9000)
- VLAN-aware bridging (supports VLANs 2-4094)
- 802.3ad LACP bonding
CEPH Storage:
- Multi-OSD configuration (2× 4TB NVMe per node)
- MTU 9000 for storage networks
- Public/private network separation
- Health monitoring and diagnostics
API Automation:
- Python via proxmoxer library
- Ansible via community.general.proxmox_* modules
- Terraform via Telmate/proxmox provider
Cluster Architecture (Matrix)
Hardware: 3× MINISFORUM MS-A2
- AMD Ryzen 9 9955HX (16C/32T)
- 64GB DDR5 @ 5600 MT/s
- 3× NVMe: 1× 1TB boot, 2× 4TB CEPH OSDs
- 4× NICs: 2× 10GbE SFP+, 2× 2.5GbE
Nodes: Foxtrot, Golf, Hotel
Quick Examples
Clone template to VM:
qm clone 9000 101 --name web-01
qm set 101 --ipconfig0 ip=192.168.3.100/24,gw=192.168.3.1
qm set 101 --net0 virtio,bridge=vmbr0,tag=30
qm start 101
Check cluster health:
uv run tools/cluster_status.py
uv run tools/check_ceph_health.py
What ships with it
15 files 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.
- anti-patterns/common-mistakes.md 7.5 KB
- examples/01-basic-vm/main.tf 3.7 KB
- examples/01-basic-vm/README.md 5.3 KB
- examples/01-basic-vm/variables.tf 924 B
- reference/api-reference.md 8.4 KB
- reference/cloud-init-patterns.md 3.8 KB
- reference/networking.md 7.2 KB
- reference/qemu-guest-agent.md 9.0 KB
- reference/storage-management.md 8.9 KB
- tools/check_ceph_health.py 16 KB runs code
- tools/check_cluster_health.py 11 KB runs code
- tools/cluster_status.py 8.8 KB runs code
- tools/validate_template.py 7.3 KB runs code
- workflows/ceph-deployment.md 22 KB
- workflows/cluster-formation.md 17 KB
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 · 89 lines · 84 tokens per session scan A b8a4d4aefee7
proxmox-infrastructure is a skill published in the GitHub repository basher83/lunar-claude (23 stars, last pushed yesterday), licensed MIT. It adds 84 tokens to every session and 865 once invoked, about $0.0004 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
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-cloud-filestore-autoscale
Inspects Google Cloud Filestore capacity and utilization, evaluates storage scaling rules, and performs capacity autoscaling (scale UP for low free space or scale DOWN for cost optimization). Use when monitoring Filestore instance headroom, resizing instance shares, configuring automated growth/shrink thresholds…
terraform-module-library
Build reusable Terraform modules for AWS, Azure, GCP, and OCI infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.
vast-gpu
Rent, manage, and destroy GPU instances on vast.ai. Use when user says "rent gpu", "vast.ai", "rent a server", "cloud gpu", or needs on-demand GPU without owning hardware.
aws-lambda-microvms
Builds, runs, debugs, and operates applications on AWS Lambda MicroVMs — Firecracker-isolated, snapshot-resumable serverless compute environments running inside a container with up to 8 hr lifetimes. Applicable when workloads need strong isolation between tenants, isolated serverless compute, sandbox compute, or…
doca-hardware-safety
Use this skill whenever the agent is about to recommend or apply a change that touches DPU / NIC hardware state on a live system — mlxconfig firmware-parameter write, NIC firmware burn, BFB reflash, NIC ↔ DPU mode flip, SR-IOV or device-emulation slot enable, kernel boot-parameter change (IOMMU, hugepages, VFIO), PCIe…