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 instructions/netboxlabs/netbox-best-practices/agents-mdgit clone --depth 1 https://github.com/netboxlabs/netbox-best-practicesWrote 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/netboxlabs/netbox-best-practices/agents-md)<a href="https://agentmods.dev/instructions/netboxlabs/netbox-best-practices/agents-md"><img src="https://agentmods.dev/badge/instructions/netboxlabs/netbox-best-practices/agents-md.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.00779 | $0.00779 |
| Opus 5 | $0.00390 | $0.00390 |
| Sonnet 5 | $0.00156 | $0.00156 |
| Haiku 4.5 | $0.00078 | $0.00078 |
Grade A, and why
netbox-best-practices 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 5d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - NetBox Best Practices
This repository contains best practices for NetBox API integrations. The content is available in multiple formats for different AI coding assistants and human readers.
Quick Start
When working on NetBox integrations, follow these key principles:
- Use v2 tokens on NetBox 4.5+ (
Bearer nbt_<key>.<token>) - Always paginate list requests - NetBox defaults to 50 items
- Use brief mode (
?brief=True) and exclude config_context for performance - Use Diode for high-volume data ingestion (handles dependencies automatically)
- Use pynetbox for Python integrations
Content Locations
| Format | Location | Audience |
|---|---|---|
| Human Documentation | HUMAN.md |
Engineers/developers |
| Claude Code Skills | skills/*/SKILL.md |
Claude Code users |
| Cursor Rules | .cursor/rules/*.mdc |
Cursor IDE users |
| Detailed Rules | skills/*/references/rules/*.md |
All (authoritative source) |
Available Rules by Category
Authentication (auth-)
- Use v2 tokens on NetBox 4.5+ (CRITICAL)
- Use provisioning endpoint for automated token creation
REST API (rest-)
- Always paginate list requests (HIGH)
- Use bulk operations via list endpoints (CRITICAL)
- Use PATCH for partial updates, not PUT
- Use brief mode and field selection for performance
- Avoid
?q=search filter at scale
GraphQL (graphql-)
- Use netbox-graphql-query-optimizer (CRITICAL)
- Always paginate, including nested lists (CRITICAL)
- Keep query depth ≤3
- Select only needed fields
Performance (perf-)
- Exclude config_context from device queries
- Use brief mode for large list operations
Data Modeling (data-)
- Create objects in dependency order (CRITICAL)
- Understand site/location hierarchy
- Use natural keys for queries
- Properly structure custom fields and tags
Integration (integ-)
- Use Diode for high-volume ingestion (HIGH)
- Use pynetbox for Python integrations (HIGH)
- Use branching plugin for change management workflows (HIGH) - requires netbox-branching
- Configure webhooks for change notifications
- Query object changes for audit trails
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.
- 5d ago First seen · 81 lines · 779 tokens per session scan A 56fdab3e29ea
netbox-best-practices AGENTS.md is an instructions file published in the GitHub repository netboxlabs/netbox-best-practices (29 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 779 tokens to every session, about $0.0039 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).