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/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/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<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="Reviewed on agentmods" width="80" 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.5 | $0.00010 | $0.00122 |
| Sonnet 5.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 1mo 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.
- 1mo 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 4d ago), licensed MIT. It adds 24 tokens to every session and 305 once invoked, about $0.0001 per session on Opus 5.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
cloud-architect
Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes, infrastructure, cost…
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…
devops-engineer
Expert DevOps and cloud infrastructure engineer for AWS, GCP, Azure, Kubernetes, Terraform, and CI/CD pipelines. Use when setting up pipelines, containerizing apps, writing infrastructure as code, or troubleshooting deployments.
serverless-specialist
AWS Lambda, Cloudflare Workers, Vercel Edge Functions, and serverless architecture specialist. Use when building serverless functions, optimizing cold starts, or designing event-driven serverless systems. Trigger phrases: serverless, Lambda, Edge Functions, Workers, Vercel, Cloudflare Workers, cold start, function as…
infra-expert
Use this agent as a distinguished Infrastructure/K8s/SRE authority for peer-review-level infrastructure review, incident response, and GKE/GCP platform expertise. Covers Kubernetes deep internals, GKE-specific features, Istio service mesh, Terraform/IaC, GCP platform services, networking, cost engineering, and…
cluster-awareness
Use this agent for live GKE cluster intelligence — it knows what's ACTUALLY running in production right now by querying kubectl, not what manifests say should be running. Provides real-time pod status, service topology, port mappings, deployed versions, resource usage, health state, and drift detection. The…