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.
git 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/rules/netboxlabs/netbox-best-practices/netbox-integration)<a href="https://agentmods.dev/rules/netboxlabs/netbox-best-practices/netbox-integration"><img src="https://agentmods.dev/badge/rules/netboxlabs/netbox-best-practices/netbox-integration/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/rules/netboxlabs/netbox-best-practices/netbox-integration"><img src="https://agentmods.dev/badge/rules/netboxlabs/netbox-best-practices/netbox-integration.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.00000 | $0.01200 |
| Opus 5.5 | $0.00000 | $0.00480 |
| Sonnet 5.5 | $0.00000 | $0.00240 |
| Haiku 4.5 | $0.00000 | $0.00120 |
Grade A, and why
netbox-integration scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
response = requests.get( How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NetBox Integration Best Practices
Use Diode for Simplified Ingestion (HIGH)
For data ingestion, use Diode instead of direct REST API.
Benefits:
- Automatic dependency resolution (no need to create objects in order)
- Reference objects by name, not ID
- Single gRPC call for batch operations
- Built-in error handling
from netboxlabs.diode.sdk import DiodeClient
from netboxlabs.diode.sdk.ingester import Device, Entity
with DiodeClient(
target="https://<your-diode-host>:443/diode",
app_name="network-discovery",
app_version="1.0.0",
) as client:
device = Device(
name="switch-nyc-01",
device_type="Cisco Catalyst 9300", # By name!
manufacturer="Cisco", # Auto-created if missing
site="NYC-DC1", # Auto-created if missing
role="Access Switch",
status="active",
)
response = client.ingest([Entity(device=device)])
Use DiodeDryRunClient to test ingestion without sending to server.
Use pynetbox for Python Integrations (HIGH)
import pynetbox
nb = pynetbox.api("https://netbox.example.com", token=TOKEN)
# Automatic pagination
all_devices = nb.dcim.devices.all()
# Filtering
active_devices = nb.dcim.devices.filter(status="active", site="nyc")
# Create
new_device = nb.dcim.devices.create(name="switch-01", ...)
# Update
device = nb.dcim.devices.get(name="switch-01")
device.status = "active"
device.save()
Webhook Configuration
Configure webhooks for event-driven integrations:
# Webhook payload structure
{
"event": "created",
"timestamp": "2024-01-15T10:30:00Z",
"model": "dcim.device",
"username": "admin",
"request_id": "abc123",
"data": { ... }, # Current state
"snapshots": {
"prechange": {}, # State before change
"postchange": {} # State after change
}
}
Best practices:
- Use HTTPS endpoints
- Verify webhook signatures
- Process asynchronously (queue and acknowledge quickly)
- Handle idempotency (webhooks may be retried)
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.
- 1mo ago First seen · 174 lines · 0 tokens per session scan A ba762d47dae4
netbox-integration is a cursor rule published in the GitHub repository netboxlabs/netbox-best-practices (31 stars, last pushed 8mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,200 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
vios-deep-rtsp-sensor
Deep reference: RTSP server proxy module and sensor management module.
unifi-api
UniFi API integration guidelines and patterns.
windmill-overview
Windmill is an open-source developer platform for building internal tools, API integrations, background jobs, workflows, and user interfaces. It offers a unified system where scripts are automatically turned into sharable UIs and can be composed into flows or embedded in custom applications.
python
Python best practices and patterns for modern software development with Flask and SQLite.
django
Definitive guidelines for writing maintainable, performant, and secure Django applications, emphasizing modern best practices, clear code organization, and efficient patterns.
server-state
USE WHEN: Fetching and caching server data with TanStack Query 5: queryOptions, hooks, mutations, invalidation.