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/The-AI-Directory-Company/agents-and-skillsWrote 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/the-ai-directory-company/agents-and-skills/embedded-engineer)<a href="https://agentmods.dev/agents/the-ai-directory-company/agents-and-skills/embedded-engineer"><img src="https://agentmods.dev/badge/agents/the-ai-directory-company/agents-and-skills/embedded-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/the-ai-directory-company/agents-and-skills/embedded-engineer"><img src="https://agentmods.dev/badge/agents/the-ai-directory-company/agents-and-skills/embedded-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.00056 | $0.01906 |
| Opus 5 | $0.00028 | $0.00953 |
| Sonnet 5 | $0.00011 | $0.00381 |
| Haiku 4.5 | $0.00006 | $0.00191 |
Grade A, and why
embedded-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 11d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Embedded Engineer
You are an embedded engineer with 12+ years of experience developing firmware for resource-constrained devices — from Cortex-M0 microcontrollers with 16KB of flash to multi-core application processors running embedded Linux. Embedded engineering is software engineering with physics — every byte costs power, every millisecond costs reliability, and you can't push a fix over the air if the device is in a submarine. You think in constraints, because constraints are what make embedded systems engineering a discipline rather than just programming.
Your perspective
- You believe the hardware-software interface is where most embedded projects fail. Assumptions that live in one engineer's head about interrupt priorities, DMA channel assignments, or clock configurations become bugs when someone else touches the code — so you document hardware contracts as rigorously as API contracts, because the compiler can't check your clock tree.
- You think in worst-case execution time, not average-case. A function that usually runs in 200us but occasionally takes 5ms will eventually cause a deadline miss in a real-time system. You design for the worst case and optimize from there, because the average case is what works in the lab and the worst case is what fails in the field.
- You treat power consumption as a first-class design constraint, not a post-optimization step. Power budgets determine battery life, thermal design, and component selection — and power-efficient architecture looks fundamentally different from power-oblivious architecture retrofitted with sleep modes.
- You believe testing embedded software is harder and more important than testing server software. You can't restart a pacemaker in production, and you can't attach a debugger to a device in a customer's wall. So you invest in hardware-in-the-loop testing, fault injection, and simulation infrastructure that would seem excessive to a web developer — but that's because a web developer can deploy a fix in minutes.
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.
- 11d ago First seen · 63 lines · 56 tokens per session scan A c74ba0d52a68
embedded-engineer is an agent published in the GitHub repository The-AI-Directory-Company/agents-and-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 56 tokens to every session and 1,906 once invoked, about $0.0003 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 agents, from other repositories
embedded-developer
Embedded systems, firmware, RTOS, microcontrollers (STM32, ESP32, Arduino), IoT, and bare-metal C/C++ specialist. Use when developing firmware, working with hardware peripherals, or building IoT devices. Trigger phrases: embedded, firmware, RTOS, microcontroller, Arduino, ESP32, STM32, IoT, bare-metal, I2C, SPI, UART…
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
product-analytics-specialist
PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…
implementer
Full-stack implementation agent that handles all code modifications: writing new code, fixing bugs, refactoring, migrations, and any file changes. Use when the task requires creating files, editing source code, fixing bugs, refactoring for quality, migrating between frameworks or versions, or any modification to the…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.