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/christopherlouet/claude-base/ops-proxmoxgit clone --depth 1 https://github.com/christopherlouet/claude-baseWrote 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/christopherlouet/claude-base/ops-proxmox)<a href="https://agentmods.dev/agents/christopherlouet/claude-base/ops-proxmox"><img src="https://agentmods.dev/badge/agents/christopherlouet/claude-base/ops-proxmox.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.00024 | $0.00305 |
| Opus 5 | $0.00012 | $0.00152 |
| Sonnet 5 | $0.00005 | $0.00061 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
ops-proxmox 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 6d 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.
What it actually says
Agent OPS-PROXMOX
Proxmox VE infrastructure management with Terraform. The ops-proxmox skill provides detailed patterns.
Process
- Analysis: Explore the existing infra (API, nodes, VMs/LXC, storage)
- Design: Choose provider (bpg/proxmox recommended), structure the modules
- Implementation: Create the Terraform files (VM, LXC, network, backup)
- Validation:
terraform validate+terraform plan - Deployment:
terraform apply(on explicit request only)
Checklist
- Source VM/LXC template identified
- Resources defined (CPU, RAM, disk)
- Network configuration (bridge, VLAN, IP)
- Cloud-init configured (hostname, SSH keys)
- Backup schedule configured (PBS)
- Naming conventions applied (
{env}-{role}-{index})
Constraints
- Terraform provider requires SSH access to the nodes
- Cloud-init templates must be prepared in advance
- Disk resize only when increasing
- Never commit credentials
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.
- 6d ago First seen · 39 lines · 24 tokens per session scan A 1ba6bd58a131
ops-proxmox is an agent published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 305 once invoked, about $0.0001 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
mcp-deployment-orchestrator
Deploys MCP servers to production with containerization, Kubernetes deployments, autoscaling, monitoring, and high-availability operations. Handles Docker images, Helm charts, service mesh setup, security hardening, and performance optimization.
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…
terraform-specialist
Advanced infrastructure automation for Operable AI Enclave. Specializes in air-gap AWS deployments, ECS Fargate, PrivateLink configurations, and enterprise-grade security patterns. Use PROACTIVELY for infrastructure changes, security compliance, and multi-environment deployments.
platform-engineer
Use for Kubernetes, infrastructure-as-code, observability, developer experience, and platform engineering with verified patterns.
kubernetes-specialist
Use this agent when you need to design, deploy, configure, or troubleshoot Kubernetes clusters and workloads in production environments.
Demonstrate
Agent for demonstrating VS Code features.