New advertisers: 50% off your first month with code FIRSTMONTHSee slots

Remote BIOS tuning and firmware flashing through an IP-KVM, with before-and-after proof of changes.

version
1.1.0
GitHub stars
32
View on GitHub

What it does

  • Adds bios-profile, bios-recommend, bios-apply, bios-update, and kvm-console skills for profiling, planning, applying, and flashing firmware
  • Covers the full loop: read the board and current settings, plan changes by role, apply through the KVM, then verify from Linux
  • Enforces a fresh baseline and a checked vendor checksum before any firmware flash, with every reboot and change waiting for approval
  • Designed for admins who manage headless machines over PiKVM, JetKVM, or NanoKVM and keep machine data in a private overlay

BIOS/UEFI tuning and flashing over an IP-KVM: profile the board, role-based setting plans, verified changes, safe updates. Your machines live in a private overlay.

Add marketplace

/plugin marketplace add danielrosehill/Claude-Code-Plugins

Run it inside Claude Code once, then install the plugin below.

Install

/plugin install bios-tuning@danielrosehill

Run it inside Claude Code after adding the marketplace.

Files

Discovered from source

BIOS apply

Executes an approved plan from bios-recommend, one row at a time, and proves each change took.

Inputs

  • Machine name and plan file (<overlay>/machines/<name>/plans/*.md, status approved).

Steps

  1. Read the plan. Refuse a plan that is not approved or whose baseline is older than the last applied plan.
  2. kvm-console check. Tell the user what goes down and for how long (setup sessions run 5-10 min); get a yes.
  3. kvm-console enter-setup. Session folder: <overlay>/machines/<name>/apply-<YYYY-MM-DDTHHMM>/.
  4. For each row: a. Navigate to the setting; screenshot NN-before.png. If "Now" on screen differs from the plan, stop and ask. b. Change it; screenshot NN-after.png. Read the new value back off the screenshot.
  5. kvm-console save-exit. The save dialog's change list must equal the plan rows. Screenshot it.
  6. Verify after boot: wait for SSH, then run each row's "Linux check after" and firmware-facts.sh again (facts-<date>.json). Rows with no Linux readout are verified by the after-screenshot only: say so. Power-on-after-loss can be proven only by cutting power (smart plug); offer it, do not do it unasked.
  7. Update the plan to applied with a result column (verified-linux, verified-screen, failed), append one line to <overlay>/machines/<name>/log.md, and save new menu paths to settings_map.

Data storage

Screenshots and the updated plan under <overlay>/machines/<name>/ (scripts/overlay-paths.sh dir).

Notes

  • Changes firmware settings and reboots the machine. Each session needs the user's yes.
  • One plan per session. If a change makes the machine fail to boot: enter setup again and revert that row from the before-screenshot; if setup is unreachable, use the plan's recovery line and tell the user at once.

Readme

BIOS Tuning

Agent skills for changing motherboard BIOS/UEFI settings and flashing firmware remotely, through an IP-KVM, with a record of what was there before and proof of what changed.

The agent sees the firmware screen through the KVM's web UI (a browser it drives) and types through the KVM (over SSH to the USB HID gadget, the PiKVM API, or the browser). Linux-side checks confirm each change after boot.

Skills

SkillWhat it does
bios-profileBoard, BIOS version, latest available firmware, Secure Boot, virtualisation, memory and WoL from Linux; a screenshot baseline of every non-default setting via the KVM
bios-recommendA change plan from a role profile (always-on server, workstation, low-power box) or your own requests, with why, risk and how to verify each row
kvm-consoleCheck the KVM, reboot into setup, read the screen, send keys, save or discard
bios-applyApplies an approved plan with before/after screenshots, checks the save dialog, verifies from Linux after boot
bios-updateDownloads and checksums firmware, stages it on the ESP or KVM virtual media, flashes with the board's tool, restores settings

Reference: reference/kvm-backends.md (eyes and hands per KVM model), reference/vendor-firmware.md (setup keys, flash tools and setting names for Gigabyte, MSI, ASUS, ASRock and others; Linux readouts), reference/machines-schema.md.

Scripts (stdlib/bash only): scripts/hid-keys.py (keystrokes via SSH HID gadget or kvmd API), scripts/firmware-facts.sh (read-only firmware facts as JSON), scripts/bios-checksum.py (vendor checksum, incl. Gigabyte's 16-bit sum), scripts/make-flash-image.sh (FAT32 virtual-USB image for the flash tool), scripts/overlay-paths.sh.

Walkthrough with real screens: docs/screenshots/gigabyte-f23-to-f25/ (a full F23 -> F25 flash through a PicoKVM).

Your machines: the overlay

Nothing about your machines lives in this repo. scripts/overlay-paths.sh dir names your data folder ($BIOS_TUNING_HOME, else $CLAUDE_USER_DATA/bios-tuning, else ~/.claude-user-data/bios-tuning). It holds machines.json, per-machine facts, baselines, plans and logs. Put your own role profiles in <overlay>/roles/<name>.md to override the built-in ones.

Safety

Every reboot, setting change and flash waits for your yes. Plans record the recovery route before anything is changed. A flash needs a fresh baseline and a checked vendor checksum.

Install

claude plugins install bios-tuning@danielrosehill

License

MIT

Details

Marketplace
danielrosehill/Claude-Code-Plugins
Source
danielrosehill/BIOS-Tuning
Author
Daniel Rosehill
Category
Hardware & Maker
License
MIT

More from danielrosehill/Claude-Code-Plugins

All 264

Similar to bios-tuning

More Development Tools