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 instructions/filthyrake/damens_mcps/proxmox-mcpgit clone --depth 1 https://github.com/filthyrake/damens_mcpsWrote 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/instructions/filthyrake/damens_mcps/proxmox-mcp)<a href="https://agentmods.dev/instructions/filthyrake/damens_mcps/proxmox-mcp"><img src="https://agentmods.dev/badge/instructions/filthyrake/damens_mcps/proxmox-mcp.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.02892 | $0.02892 |
| Opus 5 | $0.01446 | $0.01446 |
| Sonnet 5 | $0.00578 | $0.00578 |
| Haiku 4.5 | $0.00289 | $0.00289 |
Grade B, and why
damens_mcps proxmox-mcp.instructions.md scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Set permissions: `chmod 600 config.json` How it starts
The opening of the file, as written. The whole thing — 454 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Path-Specific Instructions: Proxmox MCP Server
Path: proxmox-mcp/
Project Overview
The Proxmox MCP server provides virtualization platform management capabilities through the Model Context Protocol. It allows AI assistants to manage Proxmox VE (Virtual Environment) clusters, VMs, and containers.
Key Characteristics
- Architecture: Pure JSON-RPC (no MCP library)
- Transport: stdin/stdout JSON-RPC protocol
- Canonical Server:
working_proxmox_server.pyONLY - Configuration: JSON configuration file (
config.json) - Authentication: Ticket-based authentication
Critical Requirements
Server Implementation
- ONLY use
working_proxmox_server.pyas the canonical implementation - DO NOT use or modify other server files (they exist for historical reasons)
- Server reads JSON-RPC from stdin, writes to stdout
- Use stderr for debugging:
print(message, file=sys.stderr) - Supports cluster and multi-node operations
VM and Container Operations
VM/Container operations are production-critical and can cause:
- Service interruption
- Data loss
- Resource exhaustion
- Network connectivity issues
ALWAYS:
- Validate VM/Container IDs (VMIDs)
- Check resource availability before creation
- Verify node has capacity
- Log all operations with details
- Implement safety checks for destructive operations
Dangerous Operations
These operations can cause significant problems:
- VM/CT deletion - Permanent data loss
- Snapshot deletion - Cannot recover data
- Resource allocation changes - Can affect performance
- Network configuration - Can break connectivity
- Cluster operations - Can affect entire infrastructure
Configuration
Configuration File Format
{
"host": "192.168.1.50",
"port": 8006,
"username": "root@pam",
"password": "your-password",
"verify_ssl": false,
"timeout": 30,
"node": "pve-node1",
"realm": "pam"
}
Configuration File Location
- Primary:
config.jsoninproxmox-mcp/directory - Example:
config.example.json(copy toconfig.json) - NEVER commit
config.jsonfile - Set permissions:
chmod 600 config.json
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 · 454 lines · 2,892 tokens per session scan B a4d13a0cf7e0
damens_mcps proxmox-mcp.instructions.md is an instructions file published in the GitHub repository filthyrake/damens_mcps (2 stars, last pushed 5d ago), licensed MIT. It adds 2,892 tokens to every session, about $0.0145 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
aks-mcp copilot-instructions.md
Copilot instructions for Azure/aks-mcp, covering copilot instructions, project overview, architecture, high-level structure and key components.
mcp-dockhand CLAUDE.md
Claude Code instructions for strausmann/mcp-dockhand, covering claude.md — mcp-dockhand server, projektübersicht, tech stack, verzeichnisstruktur and konventionen.
mcp-dockhand copilot-instructions.md
Copilot instructions for strausmann/mcp-dockhand, covering copilot instructions — mcp-dockhand, project context, critical: verify against upstream, code review guidelines and security.
rosetta republish-assets-not-npm.instructions.md
Instructions for tikoci/rosetta: The republishassets workflow input is for GitHub Release assets and OCI tags only.
proxmox-mcp CLAUDE.md
Claude Code instructions for akmalovaa/proxmox-mcp, covering claude.md, project overview, public listings, tech stack and project structure.
homelab-mcp CLAUDE.md
Instructions for bjeans/homelab-mcp, covering claude development guide for homelab mcp, project overview, core philosophy, project structure and architecture patterns.