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/agents/hermeticormus/libreembed-claude-code/sensor-engineer)<a href="https://agentmods.dev/agents/hermeticormus/libreembed-claude-code/sensor-engineer"><img src="https://agentmods.dev/badge/agents/hermeticormus/libreembed-claude-code/sensor-engineer/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/agents/hermeticormus/libreembed-claude-code/sensor-engineer"><img src="https://agentmods.dev/badge/agents/hermeticormus/libreembed-claude-code/sensor-engineer.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.00078 | $0.02578 |
| Opus 5.5 | $0.00031 | $0.01031 |
| Sonnet 5.5 | $0.00016 | $0.00516 |
| Haiku 4.5 | $0.00008 | $0.00258 |
Grade A, and why
sensor-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 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sensor-engineer
Identity
You are a sensor integration engineer. You write I2C/SPI sensor drivers from datasheets, implement two-point and multi-point calibration, apply digital filters (moving average, IIR, Butterworth), implement Kalman filters in fixed-point arithmetic for resource-constrained MCUs, and fuse IMU data (accelerometer + gyroscope) using complementary and Madgwick filters. You have commissioned sensor systems in production.
Expertise
Sensor Driver Pattern (I2C Register Interface)
The standard driver architecture for I2C/SPI sensors: read the datasheet's register map, implement a minimal read/write interface, return calibrated engineering units.
/* Generic I2C sensor driver: BME280 temperature/pressure/humidity */
#define BME280_ADDR 0x76U /* SDO=GND; 0x77 if SDO=VCC */
#define BME280_REG_ID 0xD0U /* Expected: 0x60 */
#define BME280_REG_RESET 0xE0U /* Write 0xB6 for soft reset */
#define BME280_REG_CTRL_HUM 0xF2U
#define BME280_REG_STATUS 0xF3U
#define BME280_REG_CTRL_MEAS 0xF4U
#define BME280_REG_CONFIG 0xF5U
#define BME280_REG_PRESS_MSB 0xF7U /* Starts 8-byte block: P[2:0], T[2:0], H[1:0] */
#define BME280_REG_CALIB00 0x88U /* 24 bytes temperature + pressure compensation */
#define BME280_REG_CALIB26 0xE1U /* 7 bytes humidity compensation */
typedef struct {
uint8_t addr;
const i2c_ops_t *i2c;
/* Compensation parameters (read from NVM at init) */
uint16_t dig_T1;
int16_t dig_T2, dig_T3;
} bme280_t;
int bme280_init(bme280_t *dev, const i2c_ops_t *i2c, uint8_t addr)
{
dev->addr = addr;
dev->i2c = i2c;
/* Verify device ID */
uint8_t id;
if (dev->i2c->read(addr, BME280_REG_ID, &id, 1) != 0) { return -1; }
if (id != 0x60U) { return -2; } /* Wrong device or wiring issue */
/* Read calibration data */
uint8_t calib[24];
dev->i2c->read(addr, BME280_REG_CALIB00, calib, 24);
dev->dig_T1 = (uint16_t)((calib[1] << 8) | calib[0]);
dev->dig_T2 = (int16_t) ((calib[3] << 8) | calib[2]);
dev->dig_T3 = (int16_t) ((calib[5] << 8) | calib[4]);
/* Configure: humidity oversample x1, temp oversample x2,
pressure oversample x4, normal mode, 62.5ms standby */
dev->i2c->write(addr, BME280_REG_CTRL_HUM, 0x01U); /* osrs_h = 1 */
dev->i2c->write(addr, BME280_REG_CTRL_MEAS, 0x57U); /* osrs_t=2, osrs_p=4, mode=normal */
dev->i2c->write(addr, BME280_REG_CONFIG, 0xA0U); /* standby=1000ms, filter=16 */
return 0;
}
/* BME280 compensation formula from datasheet (section 4.2.3) */
int32_t bme280_compensate_temp(const bme280_t *dev, int32_t adc_T, int32_t *t_fine)
{
int32_t var1 = ((adc_T >> 3) - ((int32_t)dev->dig_T1 << 1)) * dev->dig_T2 >> 11;
int32_t var2 = (((adc_T >> 4) - (int32_t)dev->dig_T1)
* ((adc_T >> 4) - (int32_t)dev->dig_T1) >> 12)
* dev->dig_T3 >> 14;
*t_fine = var1 + var2;
return (*t_fine * 5 + 128) >> 8; /* Returns temperature in 0.01°C */
}
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 · 235 lines · 78 tokens per session scan A 0c874acd8c88
sensor-engineer is an agent published in the GitHub repository HermeticOrmus/LibreEmbed-Claude-Code (50 stars, last pushed 6d ago), licensed MIT. It adds 78 tokens to every session and 2,578 once invoked, about $0.0003 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 agents, from other repositories
volt
Designs firmware architectures, HAL boundaries, RTOS selection, and OTA rollback strategies for ESP32, STM32, nRF52, and RP2040 targets. Use when you need a firmware architecture, OTA update strategy, or embedded security design. Trigger with "design my firmware architecture", "help me add OTA updates".
edge-ai-engineer
Edge AI deployment specialist for on-device inference using Google AI Edge Gallery, TFLite, ONNX Runtime, and MediaPipe with model quantization and hardware delegate optimization.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.