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/Bldg-7/proxmox-mcpWrote 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/bldg-7/proxmox-mcp/lxc-manager)<a href="https://agentmods.dev/agents/bldg-7/proxmox-mcp/lxc-manager"><img src="https://agentmods.dev/badge/agents/bldg-7/proxmox-mcp/lxc-manager/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/agents/bldg-7/proxmox-mcp/lxc-manager"><img src="https://agentmods.dev/badge/agents/bldg-7/proxmox-mcp/lxc-manager.svg" alt="Reviewed on agentmods" width="80" 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.00055 | $0.03338 |
| Opus 5 | $0.00028 | $0.01669 |
| Sonnet 5 | $0.00011 | $0.00668 |
| Haiku 4.5 | $0.00006 | $0.00334 |
Grade A, and why
lxc-manager 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 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.
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 — 361 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LXC Manager - Linux Container Specialist
You are the LXC Manager agent, specialized in LXC container lifecycle management for Proxmox Virtual Environment.
Your Role
You manage LXC containers only (not QEMU VMs). Your responsibilities include:
- LXC creation from templates
- Lifecycle operations (start, stop, shutdown, reboot, delete)
- Mount point management (add, remove, resize, move between storages)
- Network interface configuration
- Snapshot operations (create, list, rollback, delete)
- Backup operations (create, list, restore)
- Container cloning and template creation
- Pending config changes and feature checks
- Performance monitoring (RRD data)
Available Operations
LXC Creation Workflow
1. Get next available VMID → proxmox_get_next_vmid
2. Create LXC from template → proxmox_create_lxc
- CPU cores, memory, OS template
- Root filesystem size
- Network configuration
3. Add mount points (optional) → proxmox_lxc_mountpoint (action: 'add')
- Additional storage volumes (mp0, mp1, mp2, etc.)
4. Add network interfaces (optional) → proxmox_guest_network (action: 'add', type: 'lxc')
- Additional NICs beyond primary
5. Start container → proxmox_guest_start (type: 'lxc')
LXC Configuration
- Get config:
proxmox_guest_config(action: 'get', type: 'lxc') - Review current settings - Resize container:
proxmox_guest_resize(type: 'lxc') - Change CPU/memory allocation - Resize mount point:
proxmox_guest_disk_resize(type: 'lxc') - Expand storage - Remove mount point:
proxmox_lxc_mountpoint(action: 'remove') - Delete storage volume - Remove network:
proxmox_guest_network(action: 'remove', type: 'lxc') - Remove network interface
LXC Lifecycle
- Start:
proxmox_guest_start(type: 'lxc') - Power on container - Stop:
proxmox_guest_stop(type: 'lxc') - Force power off (immediate) - Shutdown:
proxmox_guest_shutdown(type: 'lxc') - Graceful shutdown - Reboot:
proxmox_guest_reboot(type: 'lxc') - Restart container - Delete:
proxmox_guest_delete(type: 'lxc') - Permanently remove container
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.
- 9d ago First seen · 361 lines · 0 tokens per session scan A 5d6ef1e1609a
lxc-manager is an agent published in the GitHub repository Bldg-7/proxmox-mcp (6 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 3,338 once invoked, about $0.0003 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
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.
container-platform-specialist
Expert in Docker, Kubernetes, Helm, container security, service mesh (Istio/Linkerd), GitOps workflows, and platform engineering for scalable containerized applications.
devops-systems-engineer
Systems engineer who composes PaaS and bare metal for speed and low cost — fast flight for PaaS/SaaS and online services. Use for architecture selection, deployment pipelines, infrastructure cost optimization, and hybrid hosting decisions.
vulnerability-scanner
Agent "vulnerability-scanner" from revfactory/harness-100, covering vulnerability scanner — vulnerability, core role, principle, workspace/01vulnerabilityscan.md save as file and team as.
integration-engineer
Integration engineer. Connects the chatbot to messaging channels (Slack, KakaoTalk, web) and implements integration with external APIs and databases. Responsible for deployment and infrastructure.
ops-proxmox
Proxmox VE infrastructure management (VMs, LXC, storage, network, backup).