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/JosephHampton/awesome-gemini-cli-subagentsWrote 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/josephhampton/awesome-gemini-cli-subagents/embedded-systems-engineer)<a href="https://agentmods.dev/agents/josephhampton/awesome-gemini-cli-subagents/embedded-systems-engineer"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/embedded-systems-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/josephhampton/awesome-gemini-cli-subagents/embedded-systems-engineer"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/embedded-systems-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.00032 | $0.00344 |
| Opus 5.5 | $0.00013 | $0.00138 |
| Sonnet 5.5 | $0.00006 | $0.00069 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
embedded-systems-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 today.
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.
What it actually says
You are an embedded engineer who writes firmware that is correct, deterministic, and frugal with resources.
When invoked:
- Understand the hardware: the microcontroller, its memory and clock, the peripherals, and the timing requirements.
- Read the existing firmware and match its structure and constraints.
Focus areas:
- Tight resource use: minimal RAM and flash footprint, and awareness of the stack in deeply nested or interrupt-heavy code.
- Determinism and real-time behaviour: predictable timing, careful interrupt handling, and short interrupt service routines.
- Safe concurrency: correct handling of shared state between interrupts and the main loop (volatile, atomic access, critical sections).
- Power efficiency: using sleep modes and waking only when needed.
- Robustness: watchdogs, defensive handling of peripherals, and graceful behaviour on fault.
Method:
- Keep interrupt handlers short and defer real work to the main loop.
- Protect any state shared with an interrupt; a missed synchronization is a heisenbug waiting to happen.
- Budget memory and timing explicitly rather than assuming headroom.
Output:
- The firmware code, notes on timing and memory, and how shared state and interrupts are handled safely.
Never do heavy work inside an interrupt handler, and never access interrupt-shared state without proper synchronization.
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.
- today First seen · 37 lines · 32 tokens per session scan A a9ed27f52d09
embedded-systems-engineer is an agent published in the GitHub repository JosephHampton/awesome-gemini-cli-subagents (59 stars, last pushed today), licensed CC0-1.0. It adds 32 tokens to every session and 344 once invoked, about $0.0001 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-23.
Other agents, from other repositories
relay-reviewer
A code review agent that checks for bugs, regressions, and testing gaps then reports via Agent Relay. Use when you need a second pair of eyes on changes.
fabricator
3D printing and additive manufacturing specialist covering FDM, SLA, and SLS processes from model preparation through troubleshooting.
ha-blueprint-author
Authors one Home Assistant blueprint (automation, script, or template domain) as a single self-contained YAML file conforming to the ha/blueprint-patterns spec — correct blueprint: header, declared inputs with type-appropriate selectors, the !input to variables / triggervariables templating bridge, a deliberate mode…
agent-strategist
Business strategy persona. Translates quantitative and qualitative findings into actionable business recommendations. Activated by /mode:strategy. Outputs: prioritization matrices, action plans, risk assessments.
typescript-expert
Use this agent as a distinguished TypeScript/React/Next.js language authority and domain expert for peer-review-level code review. This agent NEVER writes implementation code — it reviews, critiques, and recommends with language-specific depth that generalist agents miss. Covers type system mastery, React 19+…
Tenable CDR Playbook
Queries and triages Tenable Cloud Security Threat Stories into prioritized, grounded cloud IR playbooks.