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/dryvist/claude-code-plugins/pxe-netbootnpx skills add dryvist/claude-code-plugins --skill pxe-netbootgit clone --depth 1 https://github.com/dryvist/claude-code-pluginsWrote 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/dryvist/claude-code-plugins/pxe-netboot)<a href="https://agentmods.dev/skills/dryvist/claude-code-plugins/pxe-netboot"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/pxe-netboot.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.00111 | $0.01699 |
| Opus 5 | $0.00056 | $0.00849 |
| Sonnet 5 | $0.00022 | $0.00340 |
| Haiku 4.5 | $0.00011 | $0.00170 |
Grade A, and why
pxe-netboot 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 yesterday.
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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PXE netboot install (legacy/unreliable remote-media hardware)
When a server's out-of-band virtual-media path (iDRAC/iLO/BMC virtual CD) is broken or unreliable, and USB-boot keeps falling through to whatever OS is already on the internal disks, PXE is the install path that actually works. This is the concrete recipe — a temporary netboot service run from an existing healthy hypervisor on the same network.
When to use this
- The BMC's virtual-media/remote-KVM path is unreliable on this generation of hardware.
- The target's internal disks already carry an OS that keeps re-booting after every USB-boot override the firmware silently drops (a known failure mode on some legacy BMC firmware: a "boot from USB next" flag that should persist behaves as one-shot).
- Any older chassis being added to the fleet later, once you have this recipe built once.
When NOT to use this
- Routine reinstall of an already-healthy node — a verified bootable USB stick is simpler.
- First install on brand-new hardware with guaranteed-blank disks — USB-boot is simpler there too; reach for PXE only once the simple path has actually failed.
Topology
Existing healthy host (same network segment as the target)
├── dnsmasq proxyDHCP + TFTP on that interface
│ → supplements the existing DHCP server with PXE-boot options only,
│ doesn't replace it
├── a plain HTTP server serving kernel + initrd + an answer/config file
└── a custom-built iPXE binary with an embedded autoexec script
Target chassis
├── BMC on its own management network — IPMI-over-LAN reachable
└── Primary NIC on the same segment as the netboot host — PXE-capable BIOS
Steps (per node)
1. Stage kernel + initrd
Build (or reuse) an auto-install image with a per-node unattended-answer file baked in, then extract just the kernel and initrd from it — you don't need to serve the whole ISO, only the two boot artifacts plus the answer file:
mkdir -p /mnt/iso /srv/http/<target>
mount -o loop /path/to/auto-install.iso /mnt/iso
cp /mnt/iso/boot/<kernel> /mnt/iso/boot/<initrd> /srv/http/<target>/
cp <answer-file> /srv/http/<target>/answer.toml
umount /mnt/iso
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.
- yesterday First seen · 162 lines · 111 tokens per session scan A 415a038df416
pxe-netboot is a skill published in the GitHub repository dryvist/claude-code-plugins (3 stars, last pushed today), licensed Apache-2.0. It adds 111 tokens to every session and 1,699 once invoked, about $0.0006 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-09-04.
Other skills, from other repositories
vast-gpu
Rent, manage, and destroy GPU instances on vast.ai. Use when user says "rent gpu", "vast.ai", "rent a server", "cloud gpu", or needs on-demand GPU without owning hardware.
omh-physical-device-readiness
This is a Hermes-native physical-device-readiness workflow skill.
dse-loop
Autonomous design space exploration loop for computer architecture and EDA. Runs a program, analyzes results, tunes parameters, and iterates until objective is met or timeout. Use when user says "DSE", "design space exploration", "sweep parameters", "optimize", "find best config", or wants iterative parameter tuning.
embedded-iot
Embedded systems firmware, microcontrollers (ESP32, STM32, Arduino, Raspberry Pi), RTOS (FreeRTOS, Zephyr), IoT protocols (MQTT, CoAP, BLE), bare-metal C/C++, and hardware peripheral interfaces (I2C, SPI, UART, GPIO). Use when developing firmware, working with microcontrollers, or building IoT devices.
wasm
WebAssembly (WASM) integration, WASI, component model, Rust/Go to WASM compilation. Use when implementing WASM modules, browser/edge compute, or polyglot runtime.
Atera Devices
Atera device monitors: HTTP, SNMP, and TCP monitor types for network devices, services, and applications, plus monitor configuration, thresholds, and polling behavior.