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/sensor)<a href="https://agentmods.dev/commands/hermeticormus/libreembed-claude-code/sensor"><img src="https://agentmods.dev/badge/commands/hermeticormus/libreembed-claude-code/sensor/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/sensor"><img src="https://agentmods.dev/badge/commands/hermeticormus/libreembed-claude-code/sensor.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.01008 |
| Opus 5.5 | $0.00009 | $0.00403 |
| Sonnet 5.5 | $0.00004 | $0.00202 |
| Haiku 4.5 | $0.00002 | $0.00101 |
Grade A, and why
sensor 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sensor
Sensor integration command: driver generation, calibration, filtering, fusion.
Trigger
/sensor <action> [options]
Actions
driver
Generate a sensor driver from a datasheet description.
/sensor driver --part bme280 --bus i2c --addr 0x76
/sensor driver --part icm42688 --bus spi --mode 0
/sensor driver --part ads1115 --bus i2c --channels 4
calibrate
Generate calibration code for a sensor.
/sensor calibrate --method 2-point --units celsius --range "-40,85"
/sensor calibrate --method multipoint --points 5 --nvm-address 0x08080000
/sensor calibrate --method temperature-compensation --coeff 0.05
filter
Generate a digital filter for sensor data.
/sensor filter --type moving-average --window 8 --dtype int32
/sensor filter --type kalman-1d --q 1 --r 10
/sensor filter --type median --window 5
/sensor filter --type butterworth --order 2 --cutoff 10Hz --sample 100Hz
fuse
Generate IMU sensor fusion code.
/sensor fuse --sensors accel+gyro --filter complementary --dt 0.01
/sensor fuse --sensors accel+gyro+mag --filter madgwick --beta 0.1
Process
- Read sensor datasheet: WHO_AM_I register, output registers, compensation formula.
- Implement init: verify WHO_AM_I, read calibration NVM, configure oversampling and ODR.
- Implement read: burst read raw output registers, apply compensation formula.
- Add calibration: two-point at minimum, store in NVM.
- Add filter: select based on noise characteristics and acceptable latency.
Output Examples
Sensor driver test sequence
/* Acceptance test for a new sensor driver */
void sensor_driver_test(void)
{
bme280_t dev;
/* 1. Init */
int rc = bme280_init(&dev, &i2c1_ops, BME280_ADDR);
TEST_ASSERT_EQUAL_INT(0, rc);
/* 2. Read and sanity-check (room temperature expected 15-35°C) */
int32_t temp_hundredths;
bme280_read_temperature(&dev, &temp_hundredths);
TEST_ASSERT_INT_WITHIN(2000, 2500, temp_hundredths); /* 5-45°C */
/* 3. Verify no I2C errors after 100 consecutive reads */
for (int i = 0; i < 100; i++) {
TEST_ASSERT_EQUAL_INT(0, bme280_read_temperature(&dev, &temp_hundredths));
}
}
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 · 117 lines · 22 tokens per session scan A 739c3ca24b07
sensor 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,008 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.