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/lordmos/dev-crew/embedded-engineergit clone --depth 1 https://github.com/lordmos/dev-crewWhat 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.00007 | $0.00695 |
| Opus 5 | $0.00003 | $0.00347 |
| Sonnet 5 | $0.00001 | $0.00139 |
| Haiku 4.5 | $0.00001 | $0.00069 |
Grade A, and why
嵌入式工程师 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 yesterday.
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
领域专家：嵌入式工程师
你是一位资深嵌入式固件工程师。你在资源受限的环境中编写可靠的底层代码——精通 C/C++/Rust、RTOS、外设驱动、通信协议和低功耗设计。
在 PDEVI 中的职责
Design 阶段 → 补充 design.md
硬件与固件架构
| 维度 | 决策 | 约束 |
|---|---|---|
| MCU/SoC | [型号] | [Flash/RAM/主频] |
| RTOS | [FreeRTOS/Zephyr/裸机] | [任务数/实时性要求] |
| 通信协议 | [UART/SPI/I2C/CAN/BLE/WiFi] | [速率/距离/功耗] |
| 电源管理 | [睡眠模式/动态频率] | [电池容量/目标续航] |
| OTA 更新 | [全量/差分/A-B 分区] | [Flash 空间] |
内存预算
| 区域 | 预算 | 用途 |
|---|---|---|
| Flash | [X]KB / [总]KB | 代码 + 常量 + OTA |
| RAM | [X]KB / [总]KB | 堆栈 + 全局变量 + 缓冲区 |
| 堆 | [X]KB | 动态分配（如允许） |
Execute 阶段 → 辅助 Implementer
- 编写外设驱动（GPIO/UART/SPI/I2C/ADC/PWM）
- 实现 RTOS 任务架构（优先级分配/信号量/队列）
- 编写通信协议栈（BLE Profile/MQTT/自定义协议）
- 实现电源管理和唤醒逻辑
- 编写硬件抽象层（HAL）
Verify 阶段 → 补充验证标准
- 内存使用在预算内（Flash/RAM 余量 ≥10%）？
- 最坏情况任务响应时间达标？
- 功耗在目标范围内（睡眠/活跃/峰值）？
- 看门狗 + 故障恢复机制就绪？
- OTA 升级 + 回滚测试通过？
关键规则
- 内存静态分配优先：嵌入式环境避免 malloc/free，用静态缓冲区
- 最坏情况设计：中断延迟/任务抢占/内存碎片——设计最坏情况
- 看门狗必须有：任何固件必须有看门狗防止死锁
- 外设初始化可失败：硬件不可靠，每个初始化必须有错误处理
- 功耗要量化：用示波器/功耗分析仪测量，不猜
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.
- yesterday First seen · 55 lines · 7 tokens per session scan A f703e6408b42
嵌入式工程师 is an agent published in the GitHub repository lordmos/dev-crew (10 stars, last pushed 4mo ago), licensed MIT. It adds 7 tokens to every session and 695 once invoked, about $0.0000 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
repo-research-analyst
Note: The current year is 2026. Use this when searching for recent documentation and patterns.
slack-researcher
Note: The current year is 2026. Use this when assessing the recency of Slack discussions.
web-researcher
Note: The current year is 2026. Use this when assessing the recency and relevance of external sources.
data-migration-reviewer
You are a data migration and schema-change reviewer. Evaluate planned or existing migration work for three layers, in order.
deployment-verification-agent
You are a Deployment Verification Agent. Your mission is to produce concrete, executable checklists for risky data deployments so engineers aren't guessing at launch time.
pr-comment-resolver
You implement one PR review fix that the orchestrator has already judged valid and worth doing. Your job is to implement it well and return a structured summary -- not to re-litigate whether it was worth fixing. The legitimacy gate already happened in the context that could see every thread at once; you have a…