Borrowing it
Nothing to install: this file belongs to luthermonson/go-proxmox. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/luthermonson/go-proxmox/main/AGENTS.mdgit clone --depth 1 https://github.com/luthermonson/go-proxmoxWrote 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/luthermonson/go-proxmox/agents-md)<a href="https://agentmods.dev/instructions/luthermonson/go-proxmox/agents-md"><img src="https://agentmods.dev/badge/instructions/luthermonson/go-proxmox/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/luthermonson/go-proxmox/agents-md"><img src="https://agentmods.dev/badge/instructions/luthermonson/go-proxmox/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.06369 | $0.06369 |
| Opus 5 | $0.03184 | $0.03184 |
| Sonnet 5 | $0.01274 | $0.01274 |
| Haiku 4.5 | $0.00637 | $0.00637 |
Grade A, and why
go-proxmox AGENTS.md 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 479 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for AI coding agents (Claude Code, Codex, etc.) working in this
repository. CLAUDE.md defers to this file.
Build, test, lint
This project uses Mage as the task runner. Targets are
defined in magefile.go and mage/.
mage test— unit tests (alias forgo testin the root package).mage test:coverage— unit tests with-race -coverprofile=coverage.txt -covermode=atomic. CI runs this.mage test:build— compile check usinggo build -tags test(thetesttag activatesbuild.go's no-opmain).mage lint— runsgolangci-lint(version pinned inmage/install/install.go; currentlyv2.8.0). Installs it on demand.mage ci— install deps, lint, coverage, build (matches the GitHub Actions job).mage test:integration— runsgo test ./tests/integration -tags "nodes containers vms"against a real PVE cluster.mage env— print the env vars the integration suite reads, masking secrets.mage endpoints:sync/mage endpoints:coverage— snapshot the upstream PVE API surface (mage/endpoints/) and diff the package's wrapper coverage against it.coveragewrites.cache/pve-api/coverage.txt(uncovered endpoints) andcoverage_by_area.txt(per-area breakdown). The repo is at 100% coverage of considered endpoints — see "Endpoint coverage tooling" below for how the by-design exclusion list works.
Run a single unit test directly with go test -run TestName from the repo root
(unit tests live in the root package). To run only one integration suite, use the
matching build tag, e.g. go test ./tests/integration -tags nodes -run TestNode.
Integration test env vars
Required before mage test:integration:
PROXMOX_URL, PROXMOX_USERNAME, PROXMOX_PASSWORD,
PROXMOX_TOKENID, PROXMOX_SECRET
Optional: PROXMOX_OTP, PROXMOX_NODE_NAME, PROXMOX_NODE_STORAGE,
PROXMOX_APPLIANCE_PREFIX, PROXMOX_ISO_URL. Integration tests are expected to
clean up after themselves — don't leave artifacts on the target cluster.
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.
- 11d ago First seen · 479 lines · 6,369 tokens per session scan A 4c4ab9fefe5f
go-proxmox AGENTS.md is an instructions file published in the GitHub repository luthermonson/go-proxmox (286 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 6,369 tokens to every session, about $0.0318 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).