LibreEmbed Claude Code plugin

Fifteen Claude Code plugins for embedded systems, from registers and bootloaders to RTOS, IoT and functional safety.

  • 52 ★ on the repository
  • Last commit
  • MIT
Plugin

Extended access

Why this level

  • Agents write drivers and edit firmware, and flash commands change the device memory.
  • Optional hooks intercept flash commands and edits to secret files.
All reasons and checks

ormus-solutions/libreembed-claude-code

Install

Works in

Manual install

/plugin marketplace add HermeticOrmus/LibreEmbed-Claude-Code

Then `/plugin install rtos-patterns@libre-embed` or any plugin of the set; `./setup.sh` installs all at once.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Agents write drivers and edit firmware, and flash commands change the device memory.
  • Optional hooks intercept flash commands and edits to secret files.

This is third-party code. Review the repository files before installing.

What it does

LibreEmbed is built for work on a board on your desk: GCC, OpenOCD and a debugger, bare metal or a 32 KB RTOS, bugs in a chip register. Each of the fifteen plugins brings a specialist agent, a command and a skill with patterns. The microcontroller core holds `arm-cortex-m`, `bare-metal`, `memory-management` and `power-management`. Communication and I/O are covered by `communication-buses`, `sensor-integration` and `iot-protocols`: I2C, SPI, UART, CAN, MQTT, BLE and LoRaWAN. The runtime is described by `rtos-patterns` (FreeRTOS and Zephyr), `embedded-linux`, `bootloader-design` and `firmware-update`. Hardware and software junctions are taken by `fpga-integration` and `debug-trace`, quality and compliance by `embedded-testing` and `safety-critical` with IEC 61508, ISO 26262 and MISRA C. The optional `libre-embed-hooks` plugin asks for confirmation before flash and erase commands and before edits to secret files.

Who it is for. Embedded and firmware engineers who bring up boards, write drivers or debug over SWD and want an agent that knows the field.

Good fit when

  • You need a FreeRTOS task layout for a sensor logger sampling at 1 kHz and writing to flash.
  • An I2C or SPI bus driver with DMA is written from scratch and mode and error handling details matter.
  • Firmware must update over the air with two banks, rollback and a signature.
  • You want protection against accidental flashing: the hook asks before `west flash` or `openocd program`.

Not a fit when

  • The project is a web stack: the plugins target GCC, debuggers and registers.
  • You need one narrow tip and a whole set of plugins with agents is too much.
  • There is no access to the board itself: the agent gives patterns but does not replace a run on hardware.

Example request

/rtos design a task structure for a sensor logger that samples four channels at 1 kHz and writes to QSPI flash every 100 ms.

Limitations

The plugins supply patterns and agent knowledge, not verified code for a specific chip, so results must be tested on hardware. Individual plugins install one by one with `/plugin install <plugin>@libre-embed`, while `./setup.sh` installs all fifteen and the hooks and needs `claude` and `jq`. The `libre-embed-hooks` hooks touch flash commands and secret files and can be skipped with the `--no-safety-hooks` flag. The repository also holds a manifest for Grok Build. Some README examples rely on the 2026 state of tools, so check OpenOCD and compiler versions against vendor documentation.

How to disable. Remove the `<plugin>@libre-embed` plugins through `/plugin` or run `./setup.sh --uninstall` for the whole set. The clone directory is removed by hand.

FAQ

How do I install LibreEmbed in Claude Code?

Run `/plugin marketplace add HermeticOrmus/LibreEmbed-Claude-Code`, then `/plugin install rtos-patterns@libre-embed` or any of the other fifteen plugins. Restart Claude Code after installing.

How do I install everything at once?

Clone the repository and run `./setup.sh` in its directory. To pick plugins use `./setup.sh --only rtos-patterns,communication-buses`, and without safety hooks `./setup.sh --no-safety-hooks`.

What does each plugin contain?

A specialist agent, a command such as `/rtos` or `/comm-bus` and a skill with a pattern library. For example `rtos-patterns` brings the `rtos-engineer` agent and the `/rtos` command.

What does the libre-embed-hooks plugin do?

It installs SessionStart, PreToolUse and PostToolUse hooks. Before flash and erase commands such as `st-flash write`, `idf.py flash`, `pyocd flash` and `nrfjprog --program`, and before edits to secret files, the agent must get your confirmation.

Does the set work with other agents?

The repository holds a Grok Build manifest and the same plugin folders load with `grok plugin marketplace add HermeticOrmus/LibreEmbed-Claude-Code`. The main workflow is built around Claude Code.

Discussion

No questions or reviews yet.

Plugins

Ten Claude Code plugins: panes and bands above the prompt, secret handling, a vague-prompt filter and memory cleanup.

PluginBroad access115Repository stars

Plugins for git, Python and accessibility in one place: 400+ skills, subagents and hooks against dangerous agent commands.

PluginExtended access60Repository stars

A set of 24 slash commands for the Claude Code CLI: commits, review, refactoring, tests and cleanup without repeating the same prompts

PluginExtended access2.8KRepository stars

A Claude Code plugin marketplace by Frad LEE: Git and GitFlow, GitHub, refactoring, memory, research, image generation and interface work

PluginExtended access596Repository stars

A marketplace of eight Claude Code plugins: session memory, research, commits, skill authoring and more.

PluginExtended access275Repository stars

A marketplace of eight Claude Code and Codex plugins: planning from a PRD, coding, PR review, self-learning and vibe sessions

PluginBroad access124Repository stars

README in short

The README explains why embedded development differs from the web: a GCC, OpenOCD and debugger chain and a "compile, flash, watch the LED" loop. It covers fifteen plugins by group, three install routes, learning paths for three levels and compatibility.

README badge

Report a problem