Borrowing it
Nothing to install: this file belongs to netboxlabs/netbox-best-practices. 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/netboxlabs/netbox-best-practices/main/CLAUDE.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/claude-md)<a href="https://agentmods.dev/instructions/netboxlabs/netbox-best-practices/claude-md"><img src="https://agentmods.dev/badge/instructions/netboxlabs/netbox-best-practices/claude-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.1 | $0.02455 | $0.02455 |
| Opus 5 | $0.01228 | $0.01228 |
| Sonnet 5 | $0.00491 | $0.00491 |
| Haiku 4.5 | $0.00246 | $0.00246 |
Grade A, and why
netbox-best-practices CLAUDE.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 6d 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 — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md - NetBox Skills Maintenance Guide
This repository contains best practices for NetBox integrations, available in multiple formats for different AI coding assistants and human readers. This guide explains the structure, conventions, and maintenance procedures.
Repository Structure
netbox-best-practices/
├── CLAUDE.md # This file - maintenance guide
├── AGENTS.md # Cursor/general AI assistant guide
├── HUMAN.md # Human-readable guide (for engineers)
├── README.md # Repository overview
├── .cursor/rules/ # Cursor IDE rules
│ ├── netbox-auth.mdc
│ ├── netbox-rest-api.mdc
│ ├── netbox-graphql.mdc
│ ├── netbox-data-modeling.mdc
│ ├── netbox-integration.mdc
│ └── netbox-performance.mdc
└── skills/
└── netbox-integration-best-practices/
├── SKILL.md # Main skill definition (for Claude Code)
└── references/
├── netbox-integration-guidelines.md # Technical reference
└── rules/
├── _sections.md # Category definitions
├── _template.md # Rule template
└── [individual rule files]
Multi-Format Content
This repository maintains content in three parallel formats:
| Format | Location | Audience | Style |
|---|---|---|---|
| Claude Code Skills | skills/*/SKILL.md, references/ |
Claude Code users | Progressive disclosure, reference files |
| Cursor Rules | .cursor/rules/*.mdc |
Cursor IDE users | Concise (<500 lines), YAML frontmatter |
| Human Documentation | HUMAN.md |
Engineers | Concise orientation, all skills combined |
The authoritative source for all rules is skills/*/references/rules/*.md. The other formats are derived from and must stay aligned with these detailed rule files.
Important: HUMAN.md is a single document covering ALL best practices across all skills. When adding new skills, add their content to this document rather than creating skill-specific human docs.
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.
- 6d ago First seen · 301 lines · 2,455 tokens per session scan A ea7db101e110
netbox-best-practices CLAUDE.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 2,455 tokens to every session, about $0.0123 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).
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).
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.
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.