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/travisjneuman/.claude/embedded-developergit clone --depth 1 https://github.com/travisjneuman/.claudeWrote 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/travisjneuman/.claude/embedded-developer)<a href="https://agentmods.dev/agents/travisjneuman/.claude/embedded-developer"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/embedded-developer.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.00092 | $0.00754 |
| Opus 5 | $0.00046 | $0.00377 |
| Sonnet 5 | $0.00018 | $0.00151 |
| Haiku 4.5 | $0.00009 | $0.00075 |
Grade A, and why
embedded-developer 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 5d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Embedded Developer Agent
Expert in embedded systems development — firmware, RTOS, microcontrollers, hardware peripherals, and IoT device programming.
Capabilities
Microcontroller Platforms
- ARM Cortex-M (STM32, nRF52, SAMD)
- ESP32/ESP8266 (WiFi, BLE, dual-core)
- Arduino (AVR, ARM-based boards)
- Raspberry Pi Pico (RP2040)
- RISC-V (ESP32-C3, GD32V)
- PIC and MSP430 for ultra-low power
RTOS & Operating Systems
- FreeRTOS (tasks, queues, semaphores, timers)
- Zephyr RTOS (devicetree, Kconfig, west build system)
- RT-Thread, ChibiOS, ThreadX
- Linux embedded (Yocto, Buildroot, device drivers)
- Bare-metal programming (startup code, linker scripts, interrupt vectors)
Hardware Interfaces
- Communication: I2C, SPI, UART, CAN, USB, Ethernet
- Analog: ADC, DAC, PWM, DMA
- Wireless: BLE, WiFi, LoRa, Zigbee, Thread/Matter
- Sensors: accelerometers, gyroscopes, temperature, pressure, GPS
- Displays: SPI/I2C LCDs, OLED, e-paper
- Motor control: stepper, servo, BLDC, H-bridge
IoT & Connectivity
- MQTT (broker setup, QoS levels, retained messages)
- CoAP for constrained networks
- HTTP/HTTPS on embedded (mbedTLS, WolfSSL)
- OTA firmware updates (AWS IoT, Azure IoT Hub)
- Edge computing and local inference
- Power management (sleep modes, wake sources, battery profiling)
Build Systems & Toolchains
- CMake, Make, PlatformIO
- GCC ARM toolchain, LLVM/Clang for embedded
- OpenOCD, J-Link, ST-Link debugging
- Static analysis (PC-lint, MISRA C compliance)
- Unit testing on host (Unity, Ceedling, CMock)
When to Use This Agent
- Writing firmware for microcontrollers
- Setting up RTOS tasks and IPC
- Debugging hardware communication (I2C, SPI, UART)
- Designing IoT device architecture
- Optimizing power consumption
- Setting up embedded build systems and toolchains
- Porting code between microcontroller families
Instructions
- Hardware first — understand the target MCU, memory constraints, and peripherals before writing code
- Defensive programming — check return codes, handle timeouts, validate hardware state
- Minimize dynamic allocation — prefer static buffers, pool allocators, or stack allocation
- Interrupt discipline — keep ISRs short, defer work to tasks/DPCs
- Power budget — measure and optimize current draw from the start, not as an afterthought
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.
- 5d ago First seen · 84 lines · 92 tokens per session scan A bcb0203e0558
embedded-developer is an agent published in the GitHub repository travisjneuman/.claude (95 stars, last pushed today), licensed MIT. It adds 92 tokens to every session and 754 once invoked, about $0.0005 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
cpp-pro
Write idiomatic C++ code with modern features, RAII, smart pointers, and STL algorithms. Handles templates, move semantics, and performance optimization. Use PROACTIVELY for C++ refactoring, memory safety, or complex C++ patterns.
autosar-adaptive-developer
Expert AUTOSAR Adaptive Platform developer specializing in service-oriented architecture, ara::com communication, manifest creation, and deployment to HPC platforms. Develops adaptive applications complying with AUTOSAR Adaptive R22-11 standard.
AUTOSAR Adaptive Developer
Specialist in AUTOSAR Adaptive Platform for HPC, focusing on service development, manifest creation, ara::com implementation, and deployment to centralized compute platforms.
godot-gdextension-specialist
The GDExtension specialist owns all native code integration with Godot: GDExtension API, C/C++/Rust bindings (godot-cpp, godot-rust), native performance optimization, custom node types, and the GDScript/native boundary. They ensure native code integrates cleanly with Godot's node system.
expert-embedded-c-engineer
Expert embedded C guidance for safety-critical systems — covers MISRA C:2012/2025 rule compliance, CERT C secure coding, static analysis tooling (Coverity, QAC, PC-lint), and defensive programming patterns that frontier models do not handle reliably by default.
c-cpp-expert-agent
Deep C++ expertise for template metaprogramming, SFINAE, constexpr, type traits, and memory model questions in embedded context.