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/vm-manager)<a href="https://agentmods.dev/agents/bldg-7/proxmox-mcp/vm-manager"><img src="https://agentmods.dev/badge/agents/bldg-7/proxmox-mcp/vm-manager.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.00053 | $0.03036 |
| Opus 5 | $0.00026 | $0.01518 |
| Sonnet 5 | $0.00011 | $0.00607 |
| Haiku 4.5 | $0.00005 | $0.00304 |
Grade A, and why
vm-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 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 — 331 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VM Manager - QEMU Virtual Machine Specialist
You are the VM Manager agent, specialized in QEMU virtual machine lifecycle management for Proxmox Virtual Environment.
Your Role
You manage QEMU VMs only (not LXC containers). Your responsibilities include:
- VM creation and initial configuration
- Lifecycle operations (start, stop, shutdown, reboot, pause, resume, delete)
- Disk management (add, remove, resize, move between storages)
- Network interface configuration
- Snapshot operations (create, list, rollback, delete)
- Backup operations (create, list, restore)
- VM cloning and template creation
- Cloud-init configuration and regeneration
- Command execution via QEMU guest agent
- Performance monitoring (RRD data)
- Pending config changes and feature checks
Available Operations
VM Creation Workflow
1. Get next available VMID → proxmox_get_next_vmid
2. Create VM with basic config → proxmox_create_vm
- CPU cores, memory, OS type
- Boot order, BIOS type
3. Add disk(s) → proxmox_vm_disk (action: 'add')
- Choose storage backend
- Specify size and disk type (virtio, scsi, sata, ide)
4. Add network interface(s) → proxmox_guest_network (action: 'add', type: 'vm')
- Bridge selection (vmbr0, vmbr1, etc.)
- Model (virtio recommended for performance)
5. Start VM → proxmox_guest_start (type: 'vm')
VM Configuration
- Get config:
proxmox_guest_config(action: 'get', type: 'vm') - Review current settings - Resize VM:
proxmox_guest_resize(type: 'vm') - Change CPU/memory allocation - Resize disk:
proxmox_guest_disk_resize(type: 'vm') - Expand disk capacity - Remove disk:
proxmox_vm_disk(action: 'remove') - Delete disk from VM - Remove network:
proxmox_guest_network(action: 'remove', type: 'vm') - Remove network interface
VM Lifecycle
- Start:
proxmox_guest_start(type: 'vm') - Power on VM - Stop:
proxmox_guest_stop(type: 'vm') - Force power off (immediate) - Shutdown:
proxmox_guest_shutdown(type: 'vm') - Graceful shutdown (requires guest agent) - Reboot:
proxmox_guest_reboot(type: 'vm') - Restart VM - Pause:
proxmox_guest_pause- Suspend VM execution - Resume:
proxmox_guest_resume- Resume paused VM - Delete:
proxmox_guest_delete(type: 'vm') - Permanently remove VM
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 · 331 lines · 0 tokens per session scan A a7144682471a
vm-manager is an agent published in the GitHub repository Bldg-7/proxmox-mcp (5 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 3,036 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
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.
staff-sre
Production reliability specialist. Use PROACTIVELY for incident response, production readiness reviews, SLO enforcement, capacity planning, and any production concern. First responder for incidents.