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/lhbsaa/embedded-dev-skill/embedded-driver-designnpx skills add lhbsaa/embedded-dev-skill --skill embedded-driver-designgit clone --depth 1 https://github.com/lhbsaa/embedded-dev-skillWrote 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/skills/lhbsaa/embedded-dev-skill/embedded-driver-design)<a href="https://agentmods.dev/skills/lhbsaa/embedded-dev-skill/embedded-driver-design"><img src="https://agentmods.dev/badge/skills/lhbsaa/embedded-dev-skill/embedded-driver-design.svg" alt="Measured on agentmods" 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 | $0.00026 | $0.01121 |
| Opus 5 | $0.00013 | $0.00561 |
| Sonnet 5 | $0.00005 | $0.00224 |
| Haiku 4.5 | $0.00003 | $0.00112 |
Grade A, and why
embedded-driver-design 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 4d 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Embedded Driver Design
Overview
Create implementation plan assuming engineer has zero context and questionable taste. Document everything needed: files, code, testing, verification steps.
Context: Run after embedded-brainstorming approval.
Save plans to: docs/embedded/plans/YYYY-MM-DD-<driver>-plan.md
Process
1. Load Design Spec
read docs/embedded/specs/YYYY-MM-DD-<feature>-spec.md
2. Load References
Based on task type:
| Task Type | Reference File |
|---|---|
| Driver dev | references/chips.md + hardware-interfaces.md |
| Protocol | references/protocols.md |
| GUI | references/gui-feedback.md |
| Debugging | references/debugging.md |
3. Define File Structure
Map files BEFORE defining tasks:
| File | Responsibility |
|---|---|
include/driver.h |
API declarations, constants |
src/driver.c |
Implementation |
src/driver_test.c |
Unit tests (if applicable) |
4. Create Bite-Sized Tasks
Each step = ONE action (2-5 minutes):
### Task 1: Driver Header
**Files:**
- Create: `include/lcd_st7789.h`
- [ ] **Step 1: Write header file**
```c
#ifndef LCD_ST7789_H
#define LCD_ST7789_H
// ... complete code
#endif
- Step 2: Build to verify syntax
Run: idf.py build
Expected: No errors in header
- Step 3: Commit
git add include/lcd_st7789.h
git commit -m "feat: add ST7789 header"
Task 2: Driver Implementation
Files:
-
Create:
src/lcd_st7789.c -
Modify:
include/lcd_st7789.h(if needed) -
Step 1: Write init function
esp_err_t lcd_st7789_init(void) {
// ... complete implementation
}
- Step 2: Write DMA-chunked write function
esp_err_t lcd_st7789_write(const uint8_t *data, size_t len) {
// Chunking for > 4092 bytes
}
- Step 3: Build
Run: idf.py build
Expected: Exit 0
- Step 4: Commit
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.
- 4d ago First seen · 214 lines · 26 tokens per session scan A 9cc320ac92be
embedded-driver-design is a skill published in the GitHub repository lhbsaa/embedded-dev-skill (9 stars, last pushed 1mo ago), licensed MIT. It adds 26 tokens to every session and 1,121 once invoked, about $0.0001 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-31.
Other skills, from other repositories
esp32-arch-review
Review ESP32 FastLED firmware architecture for RTOS safety, DMA correctness, LED driver patterns, memory management, and peripheral safety. Use before merging significant driver changes, new platform ports, or when auditing existing ESP32 FastLED code.
esp32-log-triage
Parse and classify ESP32 serial log output to identify FastLED-related errors, RMT/I2S/SPI driver faults, timing violations, RTOS issues, and crash signatures. Use when debugging unexpected device behavior, boot failures, or LED output problems on ESP32.
embedded-debug
Firmware crash analysis, stack trace decoder, and register dump interpreter for ESP32/ARM/AVR platforms. Use when debugging device crashes, panics, guru meditation errors, hard faults, or analyzing core dumps.
ci-fix
Scan all CI builds and tests, find failures, fetch error logs, and fix the code. Prioritizes unit tests, example tests, then uno, attiny85, esp32s3, esp32c6, teensy41. Use when CI is red and you need to diagnose and repair build/test failures.
memory-audit
Audit embedded code for stack overflow risks, heap fragmentation, static allocation patterns, and memory leaks. Use when investigating OOM crashes, optimizing memory usage, or reviewing memory-critical code on constrained devices.
timing-analysis
Analyze real-time constraints, ISR latency, DMA transfer times, and LED protocol timing for embedded systems. Use when debugging timing-sensitive code, optimizing frame rates, or verifying protocol compliance.