netbox-proxbox: Instructions file for Codex

AGENTS.md

netbox-proxbox AGENTS.md is an instructions file for Codex, OpenCode from emersonfelipesp/netbox-proxbox. It costs 6,402 tokens per session, scanned A, original, Apache-2.0.

Repository instructions for adding and configuring an integration between NetBox, a network-inventory system, and Proxmox, a server-virtualization platform.

In plain words
What is it for?
Use them when writing installation and configuration documentation, checking compatibility limits, or reviewing the pre-commit checklist.
Why use it?
They prevent common setup mistakes, such as using the wrong container address or omitting the encryption key needed to save credentials.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions CLAUDE.md; mentions AGENTS.md.

This is emersonfelipesp/netbox-proxbox's own configuration. It tells Codex and OpenCode how to work on netbox-proxbox itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything netbox-proxbox configures →

Reuse

Borrowing it

Nothing to install: this file belongs to emersonfelipesp/netbox-proxbox. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/emersonfelipesp/netbox-proxbox/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/emersonfelipesp/netbox-proxbox

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for netbox-proxbox AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/emersonfelipesp/netbox-proxbox/agents-md/github.svg)](https://agentmods.dev/instructions/emersonfelipesp/netbox-proxbox/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/emersonfelipesp/netbox-proxbox/agents-md"><img src="https://agentmods.dev/badge/instructions/emersonfelipesp/netbox-proxbox/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.

agentmods 80×15 button for netbox-proxbox AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/emersonfelipesp/netbox-proxbox/agents-md"><img src="https://agentmods.dev/badge/instructions/emersonfelipesp/netbox-proxbox/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 6,402 This file is loaded in full into every session.
When invoked 6,402 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.06402 $0.06402
Opus 5.5 $0.02561 $0.02561
Sonnet 5.5 $0.01280 $0.01280
Haiku 4.5 $0.00640 $0.00640

Measured today against content hash 4f85af47293d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

netbox-proxbox 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 today.

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.

AGENTS.md · 476 lines

How it starts

The opening of the file, as written. The whole thing — 476 lines — stays where its author put it; the contents beside it link to each section on GitHub.

netbox-proxbox Agent Guide

CLAUDE.md is the source repository guide. Read and follow it before making changes in this repository.

The EdgeUno repository and vendor checkout are read-only reference sources; never edit or target them. Disabled endpoints are a hard no-network gate. Console authentication, tickets, upstream URLs, secrets, and TLS decisions stay server-side. The semantic bridge exposes only its documented typed manifest, not a raw proxy. Proxbox, NetBox, and public companion plugins each own their respective configuration and credential state.

CLAUDE.md is canonical. This wrapper repeats the safety and current-state facts that an agent must have even when @CLAUDE.md expansion is unavailable:

  • Keep changes inside the canonical Emerson repository. Never target EdgeUno.
  • Preserve the public boundary and run python scripts/check_public_boundary.py.
  • The private PBS matrix checkout uses COMPANION_READ_SSH_KEY, an encrypted Actions secret containing a read-only deploy key for emersonfelipesp/netbox-pbs only. Keep credential persistence disabled and keep the private key out of tests, logs, and artifacts.
  • Scan built wheel and source archives with --artifact; the reviewed manifest covers name, domain, URL, command, path, package, service, distribution, workspace, retired contract, and private host identifiers; inspection failures are fatal.
  • Keep the persisted nmulticloud InfluxDB organization default unchanged; it is public configuration and changing it requires a separately scoped additive compatibility migration.
  • Treat disabled endpoints as a hard no-network gate.
  • Keep credentials, console tickets, upstream URLs, and TLS decisions server-side and out of browser-readable output.
  • Keep companion-plugin imports optional and lazy; enabled-but-broken companions fail at startup rather than degrading silently.
  • netbox-pbs owns PBS REST sync, managed PBS configuration, token secrets, and audited actions. A linked PBSEndpoint is inventory only and never receives its token. PBS deployment, Proxmox storage registration, and VM backups use proxbox-api for the Proxmox operations; see docs/companion-plugins/netbox-pbs.md.
  • netbox-openbao is optional. Automatic credential storage selects OpenBao only when the companion is enabled and otherwise selects local Fernet storage; explicit selections never fall back.
  • Keep Proxmox endpoint API readiness response-local: derive serialized service monitoring eligibility from non-secret endpoint metadata plus response-local SSH and RPC readiness, preserve the guarded netbox-rpc model import before endpoint overrides, read each required global setting at most once per serializer, and derive OpenBao SSH readiness from one list-wide, actor- authorized credential metadata query without resolving credential material.
  • Keep historical migrations immutable and add a migration for schema changes.
  • Keep automatic_background_tasks strictly boolean and default-enabled. Disabled startup discovery and system-monitor scheduling must preserve explicit user jobs, integrity handlers, models, migrations, and audit records. Drain only the stock unowned, unscoped one-minute monitor; restart all application and worker processes for configuration changes.
  • Keep ProxboxPluginSettings.sync_job_timeout UI-backed and bounded to 3600–604800 seconds. Resolve it when enqueueing a sync job, preserve explicit per-enqueue overrides, and never mutate the timeout of an already-running job.
  • Keep Dockerfile.oci testing-only, preserve its separate NetBox and proxbox-api Python runtimes, and keep its OCI entrypoint equivalent to the Proxmox LXC /sbin/init path. Release builds must use the single plugin/backend pairing declared in COMPATIBILITY.md only after both required PyPI APIs expose compatible, non-yanked source distributions or pure-Python universal wheels, smoke-test the amd64 manifest from the final multi-architecture index, and publish that same digest without rebuilding.
  • Convert exact Data Protection schedules through the source endpoint's discovered IANA timezone; keep unresolved timing visibly approximate and cap combined calendar node selection at 50.
  • Keep home dashboard badge and card hydration on one bounded four-worker pool; route initial requests and at most three coalesced retries per card through that pool, keep successful badge state independent from card errors, and render backend capacity responses as throttled rather than failed. Treat the Proxmox push cache as a hint and verify the cached backend endpoint identity before use.
  • Keep the cluster Virtual Machines tab's selected-row Delete action routed to NetBox's core VirtualMachine bulk-delete endpoint. Never route selected VM IDs to the parent cluster delete action; preserve the version-checked action adapter and its real-Django regression.
  • Keep per-VM HA reads endpoint-exact. The VM sync-state endpoint is authoritative; linked typed cluster and node rows must agree with it. The tab intersects that exact enabled endpoint with caller visibility. The REST route requires virtual_machine_id={netbox_vm_pk}, restricts the VM by object permission, verifies its synchronized VM ID matches the path vmid, and queries only that one enabled, visible endpoint. Invalid, unresolved, or hidden identity must fail before backend I/O.
  • Update MkDocs sources, this wrapper, CLAUDE.md, and generated llms.txt together when architecture or operator behavior changes.
  • Run focused tests, mkdocs build --strict, the public-boundary scanner, and a per-function complexity audit when executable source changes.

Read the full file on GitHub · 476 lines

Changes

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.

  1. today Changed · +5 lines · +84 tokens per session 4f85af47293d
  2. 5d ago Changed · -27 tokens per session d4b6b0ddbb48
  3. 6d ago Changed · +75 lines · +1,045 tokens per session 16c12b1feb70
  4. 10d ago Changed · +78 lines · +1,090 tokens per session 7a96ce20a7d6
  5. 13d ago Changed 0f74f25951fd
  6. 17d ago Changed · +16 lines · +206 tokens per session 75859294c178
  7. 18d ago Changed · +21 lines · +281 tokens per session 6ba2eed29ac9
  8. 19d ago Changed · +19 lines · +270 tokens per session 15b9aeff904a
  9. 20d ago Changed · +31 lines · +384 tokens per session ccc17054f690
  10. 21d ago First seen · 231 lines · 3,069 tokens per session scan A b00f24b3aac1

Subscribe to this mod's changes

netbox-proxbox AGENTS.md is an instructions file published in the GitHub repository emersonfelipesp/netbox-proxbox (606 stars, last pushed yesterday), licensed Apache-2.0. It adds 6,402 tokens to every session, about $0.0256 per session on Opus 5.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.

Related

Other instructions, from other repositories

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,786 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens