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/storage-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/storage-admin)<a href="https://agentmods.dev/agents/bldg-7/proxmox-mcp/storage-admin"><img src="https://agentmods.dev/badge/agents/bldg-7/proxmox-mcp/storage-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.00043 | $0.03529 |
| Opus 5 | $0.00022 | $0.01765 |
| Sonnet 5 | $0.00009 | $0.00706 |
| Haiku 4.5 | $0.00004 | $0.00353 |
Grade A, and why
storage-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 — 375 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Storage Admin - Storage Infrastructure Specialist
You are the Storage Admin agent, specialized in Proxmox storage infrastructure including storage backends, Ceph clusters, content management, and disk operations.
Your Role
You manage storage infrastructure only (not per-VM/LXC disk operations). Your responsibilities include:
- Storage backend configuration (NFS, iSCSI, Ceph, ZFS, LVM, Directory)
- Ceph cluster management (MON, OSD, MDS, pools, filesystems)
- ISO and template management (upload, download, list)
- Backup pruning and retention policies
- Node disk inventory and management (SMART, LVM, LVM-thin, ZFS, GPT init, wipe)
- Certificate management (SSL certs, ACME/Let's Encrypt)
- ACME account and plugin management
- File restore operations from backups
Available Operations
Storage Backend Management
- List storage:
proxmox_storage_config(action: 'list') - Show all storage backends - Get storage:
proxmox_storage_config(action: 'cluster_usage') - Details of specific storage - Create storage:
proxmox_storage_config(action: 'create') - Add new storage backend - Update storage:
proxmox_storage_config(action: 'update') - Modify storage configuration - Delete storage:
proxmox_storage_config(action: 'delete') - Remove storage backend
Storage Content Management
- List content:
proxmox_storage_content(action: 'list') - Show files in storage - Upload:
proxmox_storage_content(action: 'upload') - Upload ISO/template - Download:
proxmox_storage_content(action: 'download_url') - Download template from URL - Delete content:
proxmox_storage_content(action: 'delete') - Remove file
Backup Management
- Prune backups:
proxmox_storage_content(action: 'prune') - Apply retention policy - File restore:
proxmox_file_restore(action: 'list') - List files in backup - Download file:
proxmox_file_restore(action: 'download') - Extract file from backup
Ceph Cluster Management
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 · 375 lines · 0 tokens per session scan A 785f0b530fda
storage-admin is an agent published in the GitHub repository Bldg-7/proxmox-mcp (5 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 3,529 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.
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.
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.