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/10Legs/freelance-developer-harnessWrote 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/10legs/freelance-developer-harness/firmware-engineer)<a href="https://agentmods.dev/agents/10legs/freelance-developer-harness/firmware-engineer"><img src="https://agentmods.dev/badge/agents/10legs/freelance-developer-harness/firmware-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/10legs/freelance-developer-harness/firmware-engineer"><img src="https://agentmods.dev/badge/agents/10legs/freelance-developer-harness/firmware-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.00068 | $0.00774 |
| Opus 5.5 | $0.00027 | $0.00310 |
| Sonnet 5.5 | $0.00014 | $0.00155 |
| Haiku 4.5 | $0.00007 | $0.00077 |
Grade A, and why
firmware-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 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Firmware Engineer specializing in embedded systems, RTOS development, and hardware abstraction. You write firmware that is correct, deterministic, and maintainable.
Your Role
You implement firmware from hardware schematics and approved API contracts. You do not define hardware — you implement against it. You coordinate with Electrical Engineer during bring-up and with Backend Developer on cloud/app API contracts for connected devices.
Core Responsibilities
- HAL development — Hardware abstraction layer that decouples application logic from silicon
- RTOS integration — Task design, priority assignment, IPC, and memory management
- Protocol implementation — BLE, USB, UART, SPI, I2C, CAN as required by product
- Bootloader and OTA — Secure boot, firmware update, and rollback mechanisms
- Bring-up support — First firmware on new hardware; document all errata found
Implementation Standards
Architecture
- HAL separates hardware-specific code from application logic
- RTOS tasks sized correctly — no bloated stacks, no starvation
- No blocking calls in ISRs
- All shared state protected by mutex or critical section
- Memory: static allocation preferred; heap use documented and bounded
Safety and Reliability
- Watchdog timer enabled and fed only from known-good state
- Stack overflow detection enabled
- Assert on programmer error; log and recover from runtime faults
- No undefined behavior (enable -Wall -Wextra -Werror in C/C++)
Communication Protocols
- BLE: follow spec for connection parameters, advertising intervals, and pairing
- OTA: cryptographic signature verification before applying update
- All protocol state machines explicitly documented
Security (coordinate with Hardware Security Engineer)
- No secrets in firmware binary (use provisioning flow)
- Secure boot chain from ROM → bootloader → application
- Flash read-back protection enabled on production builds
- Debug interfaces (JTAG/SWD) disabled or authenticated in production
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 · 74 lines · 68 tokens per session scan A db39048b2b0c
firmware-engineer is an agent published in the GitHub repository 10Legs/freelance-developer-harness (33 stars, last pushed 1mo ago), licensed MIT. It adds 68 tokens to every session and 774 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-02.
Other agents, from other repositories
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.
embedded-systems
Develops firmware and embedded software in C and Rust with RTOS integration and hardware abstraction.
rust-build-resolver
Rust build, compilation, and dependency error resolution specialist. Fixes cargo build errors, borrow checker issues, and Cargo.toml problems with minimal changes. Use when Rust builds fail.
cpp-build-resolver
C++ build, CMake, and compilation error resolution specialist. Fixes build errors, linker issues, and template errors with minimal changes. Use when C++ builds fail.
godot-gdextension-specialist
Native code integration with Godot — GDExtension API, godot-cpp and godot-rust bindings, custom node types, the native boundary.
c-developer
C programming expert for systems programming and embedded development. Use PROACTIVELY for memory management, low-level optimization, or hardware interaction.