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/keep-docs-alignedgit 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.00341 | $0.00341 |
| Opus 5 | $0.00170 | $0.00170 |
| Sonnet 5 | $0.00068 | $0.00068 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
keep-docs-aligned 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 yesterday.
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
Keep documentation aligned
When you add, rename, remove, or change behavior of MCP tools, parameters, or public APIs:
- Update
README.mdin the same change — Features, New Features, and Available Tools. - Update
src/proxmox_mcp/tools/definitions.pytool descriptions to match the implementation. - Do not document tools that are not registered in
src/proxmox_mcp/server.py. - If a tool is planned but not wired yet, mark it clearly as planned — never list it as available.
- Keep examples (params, defaults, nesting/features) accurate to the code.
- If auth, install, or first-run Cursor wiring changes, update
SETUP.md(andproxmox-config/README.mdwhen config fields change).
Checklist before finishing
- Tool name and params match
@self.mcp.toolregistration inserver.py - README inventory / detail sections updated
-
definitions.pydescription updated -
SETUP.mdstill accurate for first-run (if install/auth touched) - No stale claims (e.g. endpoint counts, missing tools)
Source of truth
Registered tools live in ProxmoxMCPServer._setup_tools() in server.py. README must match that list. First-run auth/Cursor wiring: SETUP.md.
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.
- yesterday First seen · 29 lines · 341 tokens per session scan A 8480c9130920
keep-docs-aligned is a cursor rule published in the GitHub repository hackmods/cursor-proxmox-mcp (1 stars, last pushed 15d ago), licensed MIT. It adds 341 tokens to every session, about $0.0017 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other cursor rules, from other repositories
lians-memory
Current Lians task, control policy, and bounded context.
architecture-for-apps
ArchiPy clean architecture for apps — layers, import direction, and base types.
config-and-di
ArchiPy BaseConfig, FastAPIConfig/uvicorn, and DI container wiring.
using-archipy-utils
ArchiPy helpers/utils — pure utilities, AppUtils FastAPI/gRPC factories.
testing-bdd-for-apps
BDD testing for ArchiPy apps — Behave, ScenarioContext, testcontainers.
using-archipy-adapters
Using and writing adapters in ArchiPy apps — extras, ports, mocks, boundary errors.