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.
git clone --depth 1 https://github.com/HermeticOrmus/LibreEmbed-Claude-CodeWrote 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/commands/hermeticormus/libreembed-claude-code/bootloader)<a href="https://agentmods.dev/commands/hermeticormus/libreembed-claude-code/bootloader"><img src="https://agentmods.dev/badge/commands/hermeticormus/libreembed-claude-code/bootloader/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/hermeticormus/libreembed-claude-code/bootloader"><img src="https://agentmods.dev/badge/commands/hermeticormus/libreembed-claude-code/bootloader.svg" alt="Reviewed on agentmods" width="80" 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.00021 | $0.00853 |
| Opus 5.5 | $0.00008 | $0.00341 |
| Sonnet 5.5 | $0.00004 | $0.00171 |
| Haiku 4.5 | $0.00002 | $0.00085 |
Grade A, and why
bootloader 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 15d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/bootloader
Bootloader design and firmware update command: flash layout, image packaging, CRC/signature, YMODEM.
Trigger
/bootloader <action> [options]
Actions
design
Generate a complete bootloader architecture for a target MCU.
/bootloader design --mcu stm32f407 --banks dual --transport uart
/bootloader design --mcu nrf52840 --banks dual --transport ble
/bootloader design --security ecdsa-p256 --rollback otp
Generates:
- Flash layout diagram with sector addresses
- Boot decision state machine pseudocode
- Image header C struct definition
- Jump-to-application function
flash
Implement the flash programming driver.
/bootloader flash --mcu stm32f407 --sector-erase --page-write --verify
/bootloader flash --mcu samd21 --nvmctrl-page-write
Output: erase, write, verify C functions using direct register access.
verify
Generate image verification code.
/bootloader verify --method crc32
/bootloader verify --method crc32+ecdsa --curve p256
/bootloader verify --method crc32+rsa --bits 2048
sign
Generate image packaging and signing pipeline.
/bootloader sign --tool imgtool --key ecdsa-p256.pem --version 1.2.0
/bootloader sign --custom-header --magic 0xDEADBEEF
Output: imgtool or custom Python script to package and sign firmware binary.
Process
- Confirm flash layout: total flash size, sector sizes, bootloader size constraint (<32KB typical).
- Verify transport: UART YMODEM, USB DFU, CAN, or OTA (BLE/WiFi).
- Define image header format and magic number.
- Implement CRC first, add signature verification as second layer.
- Implement and test the rollback/recovery path before the happy path.
- Write-protect bootloader sectors using FLASH_OPTCR or equivalent.
Output Examples
imgtool sign command (mcuboot compatible)
# Install: pip install imgtool
imgtool sign \
--key ecdsa-p256-signing-key.pem \
--header-size 0x80 \
--align 4 \
--version 1.2.0+0 \
--slot-size 0x38000 \
firmware_unsigned.bin \
firmware_signed.bin
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.
- 15d ago First seen · 107 lines · 21 tokens per session scan A d0c6ca013d2d
bootloader is a command published in the GitHub repository HermeticOrmus/LibreEmbed-Claude-Code (50 stars, last pushed 6d ago), licensed MIT. It adds 21 tokens to every session and 853 once invoked, about $0.0001 per session on Opus 5.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-10-01.
Other commands, from other repositories
debug
A command-line debugging toolkit for embedded programs using J-Link or OpenOCD, tools that connect a computer to a microcontroller for inspection.
la
A command for capturing and decoding signals with a Saleae logic analyzer, a device that records electrical digital signals over time. It supports buses such as UART, SPI, and I2C, which are common ways chips communicate with peripherals.
flash
A command for writing firmware to a microcontroller using OpenOCD, a tool that programs chips through a connected debugging probe.
test
A command for generating and running tests for embedded C code, either on a computer or on a physical development board. It creates both runnable test code and a written list of test cases.
map
A parser for Keil compiler map files, which are build reports describing where program code and data are placed in memory. It reports object sizes, memory regions, symbols, and stack or heap details.
verify
An embedded-device verification workflow that checks a development step through building, flashing firmware, debugging with J-Link, and reading serial logs. Firmware is software that runs directly on a microcontroller or other device.