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 skills/hermeticormus/libreembed-claude-code/embedded-testing-patternsnpx skills add HermeticOrmus/LibreEmbed-Claude-Code --skill embedded-testing-patternsgit 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.00000 | $0.01355 |
| Opus 5 | $0.00000 | $0.00678 |
| Sonnet 5 | $0.00000 | $0.00271 |
| Haiku 4.5 | $0.00000 | $0.00136 |
Grade A, and why
embedded-testing-patterns 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
embedded-testing-patterns
Knowledge Base
Embedded C test patterns using Unity, CMock, Ceedling, and QEMU.
Pattern 1: Ceedling Project Structure
project/
├── project.yml # Ceedling configuration
├── src/
│ ├── sensor.c
│ └── sensor.h
├── test/
│ ├── test_sensor.c
│ └── support/ # Test helpers, stubs
└── vendor/ # Unity, CMock (git submodule or gem)
Minimal project.yml:
:project:
:build_root: build
:test_file_prefix: test_
:paths:
:source: ["src/**"]
:test: ["test/**"]
:include: ["src"]
:tools:
:test_compiler:
:arguments:
- -std=c11
- -DUNIT_TEST
:plugins:
:load_paths: ["vendor/ceedling/plugins"]
:enabled: [gcov, xml_tests_report]
:cmock:
:enforce_strict_ordering: TRUE
:plugins: [:ignore, :return_thru_ptr, :callback]
Run:
ceedling test:all # All tests
ceedling test:sensor # Single module
ceedling gcov:all # Coverage
ceedling utils:gcov # HTML coverage report
Pattern 2: Testable HAL Interface Pattern
The golden rule: drivers never call HAL_I2C_Master_Transmit directly. They call through a pointer.
/* hal_i2c.h */
typedef int (*i2c_write_fn)(uint8_t dev_addr, uint8_t reg_addr,
const uint8_t *data, uint8_t len);
typedef int (*i2c_read_fn)(uint8_t dev_addr, uint8_t reg_addr,
uint8_t *data, uint8_t len);
typedef struct {
i2c_write_fn write;
i2c_read_fn read;
} i2c_ops_t;
/* sensor.c uses i2c_ops_t, not HAL directly */
static const i2c_ops_t *s_i2c;
int sensor_begin(const i2c_ops_t *i2c_ops) {
s_i2c = i2c_ops;
return s_i2c->write(SENSOR_ADDR, REG_RESET, (uint8_t[]){0xB6}, 1);
}
Production: pass a &stm32_i2c_ops that wraps HAL_I2C_Master_Transmit.
Test: pass a &mock_i2c_ops backed by function pointers set by CMock.
Pattern 3: CMock Expect Chaining
Order matters. CMock verifies calls happen in declared order when enforce_strict_ordering: TRUE.
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 · 183 lines · 0 tokens per session scan A fe2f3a1db7a4
embedded-testing-patterns is a skill published in the GitHub repository HermeticOrmus/LibreEmbed-Claude-Code (44 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,355 tokens. 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 skills, from other repositories
esp32-test-plan
Generate a structured multi-layer test plan for FastLED changes targeting ESP32. Covers host unit tests, WASM compile checks, platform compile checks, and hardware validation. Use after defining an implementation contract, before writing any code.
hardware-iot-bus
Low-level I2C and SPI bus peripheral control for embedded Linux boards (Orange Pi, Raspberry Pi, RISC-V).
aether-iot-query
Use this skill when the user asks about a live AetherEdge runtime: channels, points, real-time values, history, alarms, rules, models, instances, routing, SHM health, service health, or system status. Use aether CLI commands to answer — do NOT inspect source code, local database files, or config YAMLs to answer…
aether-iot
Build, integrate, diagnose, or generate applications for the AetherEdge AI-native edge kernel. Use for AetherEdge onboarding, SDK compositions, device and topology clients, read-only operations UIs, MCP integration, Domain Packs, or governed IoT commands where live-state authority and physical-device safety must be…
avr-bare-metal-embedded
Curated Knowledge API for AI Agents — 68 MCP tools, 200+ skill packs, 46K chunks, semantic search over 670K vectors, 5-layer validation pipeline. Works with Claude Code, Cursor, Cline, Windsurf.
smart-product-dev
End-to-end IoT product development orchestration for TuyaOpen projects. Guides from requirements gathering → Tuya Platform product/DP creation → complete embedded firmware generation. State-machine: detects project state and picks up from wherever development currently stands.