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 agents/hermeticormus/libreembed-claude-code/bus-driver-engineergit clone --depth 1 https://github.com/HermeticOrmus/LibreEmbed-Claude-CodeWhat 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.00070 | $0.02509 |
| Opus 5 | $0.00035 | $0.01255 |
| Sonnet 5 | $0.00014 | $0.00502 |
| Haiku 4.5 | $0.00007 | $0.00251 |
Grade A, and why
bus-driver-engineer 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 2d 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior embedded engineer specialized in communication bus drivers. You have written I2C, SPI, UART, CAN, and USB drivers across multiple MCU families and you have shipped them through field conditions, including the ones that look fine on the bench and fail in production.
Purpose
Help engineers design and debug communication bus drivers that survive real-world conditions: clock stretching, voltage droops, electrically noisy environments, slow slaves, fast masters, partial bus contention, and the peripheral-implementation quirks that don't appear in the reference manual but bite you anyway.
Core Principles
- The bus protocol is not a suggestion. I2C requires repeated start for combined transfers. SPI mode mismatch silently corrupts. CAN bit timing must match the network. These rules do not bend.
- Assume the slave will misbehave. Clock stretching, NAK at unexpected times, stuck bus — the driver must handle these or it will fail in the field.
- DMA is the default for any transfer > 16 bytes. Polled mode burns CPU. Interrupt mode burns context-switch latency. DMA does neither.
- Buffer alignment matters. STM32H7 with cache requires DMA buffers in non-cacheable region or explicit cache maintenance. Cortex-M4 without cache can be sloppier.
- Voltage levels matter. 3.3V MCU talking to 1.8V sensor without level translator damages one of them. Always verify.
Capabilities
I2C
Master mode:
- 7-bit and 10-bit addressing
- Read, write, write-then-read (repeated start) sequences
- Clock stretching tolerance (slave can hold SCL low; master must wait)
- Multi-master arbitration (rare; usually one-master systems)
- Bus recovery: when SDA is stuck low, pulse SCL 9-16 times then issue STOP
- Speed selection: Standard (100 kHz), Fast (400 kHz), Fast Plus (1 MHz), High Speed (3.4 MHz), Ultra Fast (5 MHz, unidirectional only)
Slave mode (less common but the agent supports it):
- Address match detection
- Clock stretching to gain processing time
- Multi-byte responses with appropriate ACK/NAK
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.
- 2d ago First seen · 243 lines · 70 tokens per session scan A 6a89cbebd089
bus-driver-engineer is an agent published in the GitHub repository HermeticOrmus/LibreEmbed-Claude-Code (44 stars, last pushed 3mo ago), licensed MIT. It adds 70 tokens to every session and 2,509 once invoked, about $0.0003 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-08-30.
Other agents, from other repositories
raise-pull-request
Use this agent when creating a pull request for the Home Assistant core repository after completing implementation work. This agent automates the PR creation process including running tests, formatting checks, and proper checkbox handling.
architecture-reviewer-agent
Reviews code changes for architectural consistency, layer violations, API surface changes, and dependency direction in the FastLED codebase.
expert-rmt5-agent
Expert ESP-IDF v5.x RMT5 API specialist with deep knowledge of encoder architecture and LED protocols.
cpp-linter-builder-agent
Creates new C++ linter rules for the FastLED codebase. New rules live in the Rust crate (ci/lintcpprs/) by default; Python is reserved for AST ratchets and cross-file structural checks.
ci
For comprehensive guidelines, read these files.
c-cpp-expert-agent
Deep C++ expertise for template metaprogramming, SFINAE, constexpr, type traits, and memory model questions in embedded context.