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 skills/lance0/nbox/ipam-allocatenpx skills add lance0/nbox --skill ipam-allocategit clone --depth 1 https://github.com/lance0/nboxWrote 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/skills/lance0/nbox/ipam-allocate)<a href="https://agentmods.dev/skills/lance0/nbox/ipam-allocate"><img src="https://agentmods.dev/badge/skills/lance0/nbox/ipam-allocate.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.00053 | $0.00829 |
| Opus 5 | $0.00026 | $0.00415 |
| Sonnet 5 | $0.00011 | $0.00166 |
| Haiku 4.5 | $0.00005 | $0.00083 |
Grade A, and why
nbox-ipam-allocate 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
nbox IPAM allocation
Three allocate write commands reserve the next available IP or prefix from NetBox, server-side and race-safe. All share the same dry-run / confirm / audit lifecycle (see the safe writes skill).
The three allocate commands
nbox ip reserve <prefix>
Reserve the next available IP address from a prefix.
nbox --no-tui ip reserve 10.0.0.0/24 --dry-run --json # preview
nbox --no-tui ip reserve 10.0.0.0/24 --allow-writes --confirm --json # apply
Optional: --vrf (scope the prefix), --description, --dns-name,
--message. The receipt's object is the created IP. Run nbox ip reserve --help for the full flag set.
nbox prefix reserve <cidr>
Reserve the next available child prefix from a parent prefix.
nbox --no-tui prefix 10.0.0.0/24 reserve --dry-run --json
nbox --no-tui prefix 10.0.0.0/24 reserve --length 26 --allow-writes --confirm --json
Optional: --length N (child prefix size), --vrf, --description, --message.
The receipt's object is the created prefix. Run nbox prefix reserve --help
for the full flag set.
nbox ip-range reserve <start|id>
Reserve the next available IP address from an IP range (not a prefix).
nbox --no-tui ip-range 10.0.0.10 reserve --dry-run --json
nbox --no-tui ip-range 10.0.0.10 reserve --allow-writes --confirm --json
Optional: --description, --dns-name, --message. The receipt's object is
the created IP. Run nbox ip-range reserve --help for the full flag set.
Key properties
- Server-allocated, race-safe. NetBox picks the address/block and never hands out the same one twice. The plan carries no client precondition (no ETag / last_updated) — the POST is authoritative.
- Dry-run advisory. The dry-run shows the currently next available resource as an advisory warning. NetBox allocates at apply time, so the applied resource may differ (another client could allocate between preview and apply).
- Receipt carries the created object. The
--jsonapply receipt'sobjectfield is the reserved IP or prefix view — scripts get the assigned resource without a follow-up read. - Exhaustion is a clean error. A 409 (prefix/range exhausted) or 400 (validation rejection) surfaces as exit 1, empty stdout, with the NetBox error message on stderr.
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 · 78 lines · 53 tokens per session scan A c63268cfdea2
nbox-ipam-allocate is a skill published in the GitHub repository lance0/nbox (11 stars, last pushed 2d ago), licensed Apache-2.0. It adds 53 tokens to every session and 829 once invoked, about $0.0003 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 skills, from other repositories
dcim-devices
NetBox DCIM device CRUD with foreign-key name resolution and bulk operations.
dcim-interfaces
NetBox DCIM interface CRUD with composite addressing, VLAN/LAG name resolution, and cable trace.
generic-resource-actions
Shared CRUD pattern for NetBox resources whose entire CLI surface is generated from the OpenAPI schema.
ipam-prefixes
NetBox IPAM prefix CRUD plus available-ips and available-prefixes allocation helpers.
raw
Authenticated passthrough to any NetBox /api/ path that does not yet have a typed nbx command.
config
Manage nbx NetBox URL, token, and named contexts in /.config/nbx/config.toml.