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 rules/hackmods/cursor-proxmox-mcp/lxc-exec-sshgit clone --depth 1 https://github.com/hackmods/cursor-proxmox-mcpWhat 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 | $0.00000 | $0.00454 |
| Opus 5 | $0.00000 | $0.00227 |
| Sonnet 5 | $0.00000 | $0.00091 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
lxc-exec-ssh 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 2d 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
LXC exec, guest IP, QEMU vs LXC
Hard facts (do not regress)
- Proxmox has no REST endpoint for LXC shell. Never call
/nodes/{n}/lxc/{vmid}/exec— it 501s. execute_lxc_command= opt-in configssh+ hostpct exec(paramiko). Clear error if SSH off.get_vmsis QEMU-only. LXC →get_containersorget_cluster_resources(type=vm).- Create returns UPID immediately — agents must
wait_for_taskbefore start (do not auto-wait inside create without a new decision). keyctl/fuse beyond nesting are privilege-gated; do not silently strip flags.- Prefer
bootstrap_docker_lxcwhen the user asks for a Docker LXC; fall back to raw create/prepare tools for debugging. - On keyctl 403: return structured
feature_acl_deniedwithrecommended_fallback: crun; useprepare_lxc_for_docker(docker_mode=auto|crun)orpct_set_lxc— never claim Docker-ready with nesting-only + stock runc.
When changing this area
- Update D4/D24,
agent-feedback-log.md,revisions.md, SETUP SSH section, SECURITY. - Prefer keys at create (
ssh_public_keys), orset_lxc_password(enable_password_ssh=true)after start when host SSH/pct is on. update_lxc_configdoes not set password/keys.- Create ≠ Docker/app deploy; keep success messaging honest.
- Docker path: require
nesting=1,keyctl=1when ACL allows; if keyctl denied, install Docker with modern crun asdefault-runtimeand report that fallback.
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.
- 2d ago First seen · 26 lines · 0 tokens per session scan A 52f203ec8c97
lxc-exec-ssh is a cursor rule published in the GitHub repository hackmods/cursor-proxmox-mcp (1 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 454 tokens. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other cursor rules, from other repositories
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
app_rules
This document outlines the essential rules and guidelines for developing with the MobileLauncher LT boilerplate. Follow these rules to maintain consistency, scalability, and code quality across the project.
archcore-files
Enforce MCP-only operations when working with .archcore/ files.
frontend-architecture
Vite + React SPA architecture - directory layout, providers, bundle splitting. Tailwind styling in tailwind.mdc.
database-design
Database design guidelines — relational normalisation, indexing, constraints, NoSQL patterns, query optimisation, migrations, security, and backup strategies. Applied when working with database schemas and queries.
execution
Repository execution and verification commands.