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/netboxlabs/netbox-best-practices/netbox-rest-apigit 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-rest-api)<a href="https://agentmods.dev/rules/netboxlabs/netbox-best-practices/netbox-rest-api"><img src="https://agentmods.dev/badge/rules/netboxlabs/netbox-best-practices/netbox-rest-api.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.00882 |
| Opus 5 | $0.00000 | $0.00441 |
| Sonnet 5 | $0.00000 | $0.00176 |
| Haiku 4.5 | $0.00000 | $0.00088 |
Grade A, and why
netbox-rest-api 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
response = requests.get(f"{API_URL}/dcim/devices/", headers=headers) How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NetBox REST API Best Practices
Always Paginate (HIGH)
NetBox defaults to 50 items per page (max 1000). Always handle pagination explicitly.
# WRONG: Assumes all results returned
response = requests.get(f"{API_URL}/dcim/devices/", headers=headers)
devices = response.json()["results"] # Only first 50!
# CORRECT: Paginate through all results
def get_all_objects(endpoint, limit=100):
all_results = []
url = f"{API_URL}/{endpoint}/?limit={limit}"
while url:
response = requests.get(url, headers=headers)
data = response.json()
all_results.extend(data["results"])
url = data.get("next")
return all_results
Use Brief Mode for Lists (HIGH)
Reduces payload size significantly for list operations.
# Full nested objects (slow)
response = requests.get(f"{API_URL}/dcim/devices/")
# Brief mode - minimal nested data (fast)
response = requests.get(f"{API_URL}/dcim/devices/?brief=True")
Use Field Selection (HIGH)
For more control than brief mode, specify exactly which fields to include:
# Select specific fields (including nested)
response = requests.get(
f"{API_URL}/dcim/devices/?fields=id,name,status,site.name,primary_ip4.address"
)
Exclude Expensive Fields (HIGH)
Config context and local context are expensive to compute. Exclude when not needed.
4.5.2+ Use ?omit= Parameter (#21244):
# Exclude multiple expensive fields (4.5.2+)
response = requests.get(
f"{API_URL}/dcim/devices/",
params={"omit": "config_context,local_context_data"}
)
The ?omit= parameter is the inverse of ?fields= - include everything except the specified fields.
Pre-4.5.2 Use ?exclude= Parameter:
response = requests.get(
f"{API_URL}/dcim/devices/",
params={"exclude": "config_context"}
)
Use PATCH, Not PUT (HIGH)
# WRONG: PUT replaces entire object
requests.put(f"{API_URL}/dcim/devices/123/", json=full_device_data)
# CORRECT: PATCH updates only specified fields
requests.patch(f"{API_URL}/dcim/devices/123/", json={"status": "active"})
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 · 128 lines · 0 tokens per session scan A 7b6a0e837e7c
netbox-rest-api is a cursor rule published in the GitHub repository netboxlabs/netbox-best-practices (29 stars, last pushed 6mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 882 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
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.