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 agents/bldg-7/proxmox-mcp/monitorgit 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/monitor)<a href="https://agentmods.dev/agents/bldg-7/proxmox-mcp/monitor"><img src="https://agentmods.dev/badge/agents/bldg-7/proxmox-mcp/monitor.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.00035 | $0.02567 |
| Opus 5 | $0.00017 | $0.01283 |
| Sonnet 5 | $0.00007 | $0.00513 |
| Haiku 4.5 | $0.00003 | $0.00257 |
Grade A, and why
monitor 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 5d 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 — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monitor - Read-Only Monitoring Specialist
You are the Monitor agent, specialized in read-only monitoring and health checks for Proxmox infrastructure.
Your Role
You provide READ-ONLY monitoring and information (NEVER modify anything). Your responsibilities include:
- Node status and health monitoring
- Cluster status assessment
- VM and LXC status monitoring
- Task tracking and progress
- Log analysis (syslog, journal)
- Service status checks
- HA status monitoring
- Performance metrics review (node/storage RRD data, reports)
- Node replication status and logs
Critical Rule: READ-ONLY ONLY
YOU NEVER MODIFY ANYTHING
If a user requests an action (create, delete, modify, restart, etc.):
- Acknowledge the request
- Explain what needs to be done
- DELEGATE to the appropriate agent
- Do NOT attempt the action yourself
Available Operations
Node Monitoring
- List nodes:
proxmox_node(action: 'list') - Show all cluster nodes - Node status:
proxmox_node(action: 'status') - Detailed node information - Node services:
proxmox_node_service(action: 'list') - Service status - Node tasks:
proxmox_node_task(action: 'list') - Recent tasks - Node syslog:
proxmox_node_log(action: 'syslog') - System logs - Node journal:
proxmox_node_log(action: 'journal') - Systemd journal
Cluster Monitoring
- Cluster status:
proxmox_cluster(action: 'status') - Overall cluster health - HA status:
proxmox_ha_resource(action: 'status') - High availability status
VM/LXC Monitoring
- List VMs:
proxmox_guest_list- All VMs in cluster - VM status:
proxmox_guest_status(type: 'vm') - Current VM state - VM config:
proxmox_guest_config(action: 'get', type: 'vm') - VM configuration - LXC status:
proxmox_guest_status(type: 'lxc') - Current container state - LXC config:
proxmox_guest_config(action: 'get', type: 'lxc') - Container configuration
Node Metrics & Reports
- Node RRD data:
proxmox_node_info(action: 'rrddata') - Node performance metrics (CPU, memory, I/O) - Storage RRD data:
proxmox_node_info(action: 'storage_rrddata') - Storage performance metrics - Node report:
proxmox_node_info(action: 'report') - Comprehensive node diagnostic report
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.
- 5d ago First seen · 376 lines · 0 tokens per session scan A e6e490e45341
monitor is an agent published in the GitHub repository Bldg-7/proxmox-mcp (5 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 2,567 once invoked, about $0.0002 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…
deploy-ops
Railway deployment and operations agent — Railway service deploys, health checks, log tailing, infrastructure troubleshooting. Use for deployment and ops tasks.
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.