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/proxmox-authgit clone --depth 1 https://github.com/hackmods/cursor-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/rules/hackmods/cursor-proxmox-mcp/proxmox-auth)<a href="https://agentmods.dev/rules/hackmods/cursor-proxmox-mcp/proxmox-auth"><img src="https://agentmods.dev/badge/rules/hackmods/cursor-proxmox-mcp/proxmox-auth.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 | $0.00000 | $0.00438 |
| Opus 5 | $0.00000 | $0.00219 |
| Sonnet 5 | $0.00000 | $0.00088 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
proxmox-auth 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 3d 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
Proxmox auth & Privilege Separation
When documenting, troubleshooting, or changing auth/access tools:
Token identity
- Config splits Proxmox’s
user@realm!tokenidintoauth.user+auth.token_name+auth.token_value. - Never put
user!tokeninauth.user. token_valueis the UUID secret, not the token id.
Privilege Separation
| privsep | Behavior |
|---|---|
| Yes (default, best practice) | Token needs its own ACL on user@realm!tokenid. Effective perms = user ∩ token. |
| No | Token inherits all user permissions. Lab shortcut; larger blast radius if config.json leaks. |
Empty API results / odd 401–403 with a “valid” token almost always mean privsep=Yes and no token ACL. Do not “fix” docs by recommending privsep=No as the default — document it as an explicit lab bypass and point to token ACL setup.
Docs to keep aligned
- User-facing:
SETUP.md§1,proxmox-config/README.md, README Configuration - Research:
.cursor/research/decisions.md(D8),changelog-notes.md - Tool copy:
CREATE_TOKEN_DESC/create_tokenprivsepdefaulttrueinserver.py
Safety
- Prefer dedicated
mcp@pveoverroot@pamtokens. - Optional
auth_write(D31) elevates mutations; keep privsep=Yes + ACL on both token identities. config.jsonmust stay gitignored.create_tokenreturns the secret once — never log it at INFO.
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.
- 3d ago First seen · 38 lines · 0 tokens per session scan A 563a64781acc
proxmox-auth is a cursor rule published in the GitHub repository hackmods/cursor-proxmox-mcp (1 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 438 tokens. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other cursor rules, from other repositories
viberaven-deploy
Apply before changing Vercel config or deploy CI workflows.
cloudflare-workers-hono-auto
Cloudflare Workers with Hono framework development standards and best practices.
cloudflare-workers-auto
Cloudflare Workers development standards and best practices.
aws-cloudformation
AWS CloudFormation Development Standards.
aws-eventbridge
AWS EventBridge Development Standards.
aws-iam
AWS IAM Security Best Practices.