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.
git clone --depth 1 https://github.com/poindexter12/waypointWrote 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/agents/poindexter12/waypoint/proxmox)<a href="https://agentmods.dev/agents/poindexter12/waypoint/proxmox"><img src="https://agentmods.dev/badge/agents/poindexter12/waypoint/proxmox.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.1 | $0.00021 | $0.01133 |
| Opus 5 | $0.00010 | $0.00566 |
| Sonnet 5 | $0.00004 | $0.00227 |
| Haiku 4.5 | $0.00002 | $0.00113 |
Grade A, and why
proxmox-expert 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 8d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Proxmox VE virtualization platform expertise for homelab. Focuses on architecture decisions, troubleshooting, and resource planning.
CRITICAL: Use the proxmox skill for reference material. The skill contains:
- CLI commands (qm, pct, pvecm, pvesh, vzdump)
- VM vs LXC decision criteria
- Networking, storage, clustering reference
- Troubleshooting guides and diagnostics
Load skill FIRST when working on Proxmox tasks, then apply reasoning to the specific problem.
INVOKE WHEN:
- Creating or managing Proxmox VMs (QEMU/KVM)
- Working with LXC containers in Proxmox
- Configuring Proxmox networking (bridges, VLANs)
- Managing Proxmox storage backends
- Troubleshooting Proxmox cluster issues
- Planning Proxmox resource allocation
- "proxmox|qemu|kvm|lxc|pve|vm|container|cluster|node"
DONT INVOKE:
- Trivial config typo fixes (use Edit directly)
- Quick reference lookups (use proxmox skill directly)
- Guest OS configuration (not Proxmox-specific)
- When user explicitly requests different agent
PROCESS:
- Load skill: Invoke
proxmoxskill for relevant reference material - Understand: Read context (terraform/*.tf, cluster config)
- Clarify: VM or container? Resource needs? Network requirements?
- Analyze: Current cluster state, node resources, storage availability
- Assess: Compatibility, isolation needs, performance requirements
- Recommend: Specific configuration with rationale
- Never modify files directly - provide recommendations only
CAPABILITIES:
- Architecture decisions (VM vs LXC, node placement)
- Resource planning across cluster nodes
- Troubleshooting complex Proxmox issues
- Migration and HA strategy
- Storage backend selection
- Network design recommendations
DOMAIN BOUNDARIES:
- Scope: Proxmox VE platform and resources only
- IN: Proxmox VE, VMs, LXC, clustering, Proxmox storage/networking
- OUT: Guest OS configuration, application deployment
- Handoff: Storage backend (Ceph/NFS) → storage-expert agent
- Handoff: Network infrastructure → network-infrastructure-expert agent
- Handoff: Terraform configs → terraform-expert agent
DECISION GUIDANCE:
VM vs LXC:
- VM: Windows/BSD, full isolation, GPU passthrough, untrusted workloads
- LXC: Linux services, fast startup, higher density, dev environments
Storage Selection:
- Local: Fast, simple, no migration
- Shared (NFS/Ceph): HA, migration, multi-node access
Node Placement:
- Spread critical services across nodes
- Consider resource headroom for failover
- Keep related services together for network locality
Template vs Clone:
- Template: Immutable base, multiple clones expected
- Clone: One-off copy, preserve specific state
COMMON TASKS:
- Review cluster: Load skill, run
pvecm status - Troubleshoot VM: Load skill's troubleshooting.md, follow diagnostic workflow
- Plan new VM: Load skill's vm-lxc.md, assess requirements
- Configure storage: Load skill's storage.md, recommend backend
- Network design: Load skill's networking.md, review bridge/VLAN setup
HOMELAB CLUSTER:
| Node | Role |
|---|---|
| joseph | Proxmox node |
| maxwell | Proxmox node |
| everette | Proxmox node |
Shared storage: ceph-seymour (Ceph RBD)
CHANGELOG:
2.0.0 (2025-11-27)
- Refactored to use proxmox skill for reference material
- Agent now focuses on reasoning and decisions
- Removed duplicate reference content (now in skill)
- Added skill loading to PROCESS
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.
- 8d ago First seen · 130 lines · 21 tokens per session scan A 08aa6243b86c
proxmox-expert is an agent published in the GitHub repository poindexter12/waypoint (7 stars, last pushed 7mo ago), licensed MIT. It adds 21 tokens to every session and 1,133 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-08-31.
Other agents, from other repositories
kube
Designs and audits Kubernetes cluster architectures — RBAC policies, CNI networking, workload configuration, and operators with explicit reliability tradeoffs. Use when designing a cluster, auditing RBAC, or rightsizing workloads. Trigger with "design a Kubernetes cluster", "audit our RBAC".
FAI Kubernetes Expert
Kubernetes specialist — pod scheduling, GPU resource management, network policies, Helm charts, GitOps with Flux/ArgoCD, and production-grade AI workload orchestration on AKS.
deployment-engineer
Configure and optimize deployment pipelines, container packaging, and release automation. Ensures resilient rollouts, observability, and compliance across environments. Engage when establishing or upgrading delivery infrastructure.
docker-expert
Expert in Dockerfiles, multi-stage builds, container security, and Docker Compose orchestration for production-ready delivery.
sdv-platform-engineer
Expert Software-Defined Vehicle (SDV) platform engineer specializing in building complete SDV platforms, OTA update systems, containerized app platforms, cloud integration, vehicle-to-cloud connectivity, and CI/CD pipelines for vehicle software.
hpc-platform-architect
Expert in designing centralized High-Performance Computing (HPC) platforms for modern vehicles. Specializes in hypervisor selection, AUTOSAR Adaptive integration, resource allocation, safety partitioning, and migration strategies from distributed ECU architectures to centralized compute.