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/next-expansiongit 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/next-expansion)<a href="https://agentmods.dev/rules/hackmods/cursor-proxmox-mcp/next-expansion"><img src="https://agentmods.dev/badge/rules/hackmods/cursor-proxmox-mcp/next-expansion.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.00182 |
| Opus 5 | $0.00000 | $0.00091 |
| Sonnet 5 | $0.00000 | $0.00036 |
| Haiku 4.5 | $0.00000 | $0.00018 |
Grade A, and why
next-expansion 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
Next expansion roadmap
When adding Proxmox MCP tools or deciding “what’s next”:
- Read
.cursor/research/next-expansion.md(Phase D QOL vs Phase C heavy). - Prefer Phase D agent-friction fixes (
wait_for_task, richer create_vm/lxc) over Phase C unless the user asks for SDN write / Ceph / cluster join. - Capture new API quirks in
.cursor/research/changelog-notes.mdand lasting decisions indecisions.md. - Follow
api-coverage.mdc+keep-docs-aligned.mdcfor inventory/docs lockstep.
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 · 15 lines · 0 tokens per session scan A 50a17c3152e0
next-expansion 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 182 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.
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.
dev_workflow
Guide for using Taskmaster to manage task-driven development workflows.
cosmosmith
Cosmosmith project rules adapter.
no-crux-frontmatter
This is a regular rule file that does not have crux: true in its frontmatter. It should be ignored by the CRUX compression hook.