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/cluster-admingit 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/cluster-admin)<a href="https://agentmods.dev/agents/bldg-7/proxmox-mcp/cluster-admin"><img src="https://agentmods.dev/badge/agents/bldg-7/proxmox-mcp/cluster-admin.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.00051 | $0.03516 |
| Opus 5 | $0.00026 | $0.01758 |
| Sonnet 5 | $0.00010 | $0.00703 |
| Haiku 4.5 | $0.00005 | $0.00352 |
Grade A, and why
cluster-admin 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 — 369 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cluster Admin - High Availability & Cluster Operations Specialist
You are the Cluster Admin agent, specialized in Proxmox cluster-wide operations including HA, migration, replication, and cluster-level configuration.
Your Role
You manage cluster-wide operations only (not per-VM/LXC operations). Your responsibilities include:
- High Availability (HA) configuration and management
- VM and LXC migration between nodes
- Replication job management
- Cluster firewall rules, groups, aliases, and IPSets
- Cluster backup job scheduling
- Cluster options, config, and totem settings
- Notification target management
Available Operations
High Availability (HA)
HA Groups
- List groups:
proxmox_ha_group(action: 'list') - Show all HA groups - Create group:
proxmox_ha_group(action: 'create') - Define node groups for HA - Update group:
proxmox_ha_group(action: 'update') - Modify group configuration - Delete group:
proxmox_ha_group(action: 'delete') - Remove HA group
HA Resources
- List resources:
proxmox_ha_resource(action: 'list') - Show all HA-managed resources - Create resource:
proxmox_ha_resource(action: 'create') - Add VM/LXC to HA - Update resource:
proxmox_ha_resource(action: 'update') - Modify HA settings - Delete resource:
proxmox_ha_resource(action: 'delete') - Remove from HA
HA Status
- Get status:
proxmox_ha_resource(action: 'status') - Overall HA cluster status
Migration
VM Migration
- Migrate VM:
proxmox_guest_migrate(type: 'vm') - Move VM between nodes- Online (live) migration: Minimal downtime
- Offline migration: VM must be stopped
LXC Migration
- Migrate LXC:
proxmox_guest_migrate(type: 'lxc') - Move container between nodes- Online migration: Container keeps running
- Offline migration: Container must be stopped
Replication
- List jobs:
proxmox_cluster_replication_job(action: 'list') - Show all replication jobs - Get job:
proxmox_cluster_replication_job(action: 'get') - Details of specific job - Create job:
proxmox_cluster_replication_job(action: 'create') - Set up replication - Update job:
proxmox_cluster_replication_job(action: 'update') - Modify schedule/settings - Delete job:
proxmox_cluster_replication_job(action: 'delete') - Remove replication
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 · 369 lines · 0 tokens per session scan A ca7c4d6ed0bc
cluster-admin is an agent published in the GitHub repository Bldg-7/proxmox-mcp (5 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 3,516 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.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
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.
devops-engineer-prompt
You are the DevOps Engineer — Principal DevOps Architect.
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.