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/bare-metal)<a href="https://agentmods.dev/commands/hermeticormus/libreembed-claude-code/bare-metal"><img src="https://agentmods.dev/badge/commands/hermeticormus/libreembed-claude-code/bare-metal/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/bare-metal"><img src="https://agentmods.dev/badge/commands/hermeticormus/libreembed-claude-code/bare-metal.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.00022 | $0.01006 |
| Opus 5.5 | $0.00009 | $0.00402 |
| Sonnet 5.5 | $0.00004 | $0.00201 |
| Haiku 4.5 | $0.00002 | $0.00101 |
Grade A, and why
bare-metal 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/bare-metal
Bare-metal firmware command: register-level drivers, linker scripts, startup code, and size analysis.
Trigger
/bare-metal <action> [options]
Actions
init
Generate a complete bare-metal project scaffold for a target MCU.
/bare-metal init --mcu stm32f407vg --flash 1024K --sram 128K --ccm 64K
/bare-metal init --mcu stm32f103c8 --flash 64K --sram 20K
Generates:
startup.cwith Reset_Handler and weak default ISR aliases<mcu>.ldlinker script with MEMORY regions and SECTIONSMakefilewith arm-none-eabi-gcc flags (-Os -ffunction-sections --gc-sections)main.cskeleton with SystemInit call and infinite loop
optimize
Analyze and reduce code/data size.
/bare-metal optimize --map firmware.map --target flash
/bare-metal optimize --elf firmware.elf --show-top 20
Actions:
- Parse
.mapfile for top consumers - Suggest
__attribute__((optimize("Os")))on hot paths that need size over speed - Identify padding bytes between sections
- Check for
-fno-exceptionsand-fno-rttiif C++ is mixed in
analyze-map
Decode a linker map file.
/bare-metal analyze-map firmware.map
/bare-metal analyze-map firmware.map --section .text --min-size 512
Output: table of symbol, section, size, origin file, sorted descending.
flash
Generate flash commands for common programmers.
/bare-metal flash --tool openocd --interface stlink --target stm32f4x
/bare-metal flash --tool pyocd --target stm32f407
/bare-metal flash --tool jlink --device STM32F407VG
Process
- Confirm MCU part number (determines FLASH/SRAM sizes, peripheral base addresses).
- Check if CMSIS device headers are available (
stm32f4xx.hor similar). - Generate startup and linker script matching the target's memory map exactly.
- Verify with
arm-none-eabi-sizethat sections fit within declared MEMORY regions. - Add linker
ASSERTstatements to catch overflows at link time.
Output Examples
Flash + SRAM ASSERT in linker script
/* Fail at link time if firmware exceeds flash */
ASSERT(SIZEOF(.text) + SIZEOF(.data) < LENGTH(FLASH),
"ERROR: Flash overflow")
ASSERT(SIZEOF(.data) + SIZEOF(.bss) < LENGTH(SRAM),
"ERROR: SRAM overflow")
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 · 115 lines · 22 tokens per session scan A d44d857c1643
bare-metal is a command published in the GitHub repository HermeticOrmus/LibreEmbed-Claude-Code (50 stars, last pushed 6d ago), licensed MIT. It adds 22 tokens to every session and 1,006 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.
size
A command that reads a Keil compiler .map file, a build report describing where firmware uses memory. It reports Flash, RAM, stack, and heap allocation and compares usage with warning limits.
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.