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-mcp-server/claude-mdgit clone --depth 1 https://github.com/netboxlabs/netbox-mcp-serverWrote 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-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/netboxlabs/netbox-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/netboxlabs/netbox-mcp-server/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.03311 | $0.03311 |
| Opus 5 | $0.01656 | $0.01656 |
| Sonnet 5 | $0.00662 | $0.00662 |
| Haiku 4.5 | $0.00331 | $0.00331 |
Grade A, and why
netbox-mcp-server 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 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 — 378 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NetBox MCP Server
Core Concept
A read-only Model Context Protocol server that enables LLMs to interact with NetBox infrastructure data. Built with FastMCP and designed for use by NetBox operators.
Your role: Help contributors design and implement features within the project's stated scope (see CONTRIBUTING.md). Challenge proposals that fall outside scope before implementation begins, not after. Ask clarifying questions and challenge assumptions when needed.
Tech Stack
- Python: >=3.11, <3.15
- Package Manager: uv
- MCP Framework: FastMCP >=3.0.0
- HTTP Client: httpx
- NetBox API: REST API via token authentication
Project Structure
.
├── src/
│ └── netbox_mcp_server/
│ ├── __init__.py # Package initialization with __version__
│ ├── __main__.py # Entry point for module execution
│ ├── server.py # Main MCP server with tool definitions
│ ├── netbox_client.py # NetBox REST API client abstraction
│ ├── netbox_types.py # NetBox object type mappings
│ └── config.py # Settings and logging configuration
├── tests/ # Test suite
├── .github/workflows/ # CI/CD automation
├── pyproject.toml # Dependencies and project metadata
├── README.md # User-facing documentation
├── CHANGELOG.md # Auto-generated release notes
└── LICENSE # Apache 2.0 license
Design Pattern: Clean separation between MCP server logic (server.py) and NetBox API client (netbox_client.py) to support future plugin-based implementations.
Common Commands
# Install dependencies (ONLY use uv, NEVER pip)
uv sync
# Run the server locally (requires env vars)
NETBOX_URL=https://netbox.example.com/ NETBOX_TOKEN=<token> uv run netbox-mcp-server
# Alternative: module execution
uv run -m netbox_mcp_server
# Add to Claude Code (for development/testing)
claude mcp add --transport stdio netbox \
--env NETBOX_URL=https://netbox.example.com/ \
--env NETBOX_TOKEN=<token> \
-- uv --directory /path/to/netbox-mcp-server run netbox-mcp-server
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 · 378 lines · 3,311 tokens per session scan A 0d0f11d16643
netbox-mcp-server CLAUDE.md is an instructions file published in the GitHub repository netboxlabs/netbox-mcp-server (224 stars, last pushed today), licensed Apache-2.0. It adds 3,311 tokens to every session, about $0.0166 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
blockrun-mcp AGENTS.md
AGENTS.md instructions for BlockRunAI/blockrun-mcp, covering blockrun mcp, commands, project structure, key dependencies and install in codex.
openrouter-mcp-multimodal AGENTS.md
AGENTS.md instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
intervals-icu-mcp CLAUDE.md
Claude Code instructions for hhopke/intervals-icu-mcp, covering claude.md, project overview, development commands, architecture (quick reference) and tool categories.
ai-toolkit AGENTS.md
AGENTS.md instructions for pipefy/ai-toolkit, covering repository guidelines, documentation map, project structure, import namespace migration: pipefysdk → pipefy and src/pipefysdk/init.py (transitional shim).
flyto-core CLAUDE.md
Claude Code instructions for flytohub/flyto-core, covering claude notes, cross-agent handoff and shared code intelligence.
Plonk AGENTS.md
AGENTS.md instructions for ostapondo/Plonk, covering agent rules, layout, adding a module, build & verify and code style.