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 skills add zhinkgit/embeddedskills --skill eidegit clone --depth 1 https://github.com/zhinkgit/embeddedskillsWrote 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/skills/zhinkgit/embeddedskills/eide)<a href="https://agentmods.dev/skills/zhinkgit/embeddedskills/eide"><img src="https://agentmods.dev/badge/skills/zhinkgit/embeddedskills/eide/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/skills/zhinkgit/embeddedskills/eide"><img src="https://agentmods.dev/badge/skills/zhinkgit/embeddedskills/eide.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00151 | $0.02153 |
| Opus 5.5 | $0.00060 | $0.00861 |
| Sonnet 5.5 | $0.00030 | $0.00431 |
| Haiku 4.5 | $0.00015 | $0.00215 |
Grade A, and why
eide 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 1mo 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EIDE 嵌入式工程构建
本 skill 提供 EIDE (Embedded IDE) 工程的发现、构建配置枚举、增量编译、全量重建、清理和 ELF 大小分析能力，并返回可供 jlink/openocd 继续使用的固件产物路径。
EIDE 是 VS Code 下的嵌入式开发扩展，使用 ARM CC (AC5/AC6) 或 GCC 工具链，通过 unify_builder 统一构建后端驱动。
配置
环境级配置（skill/config.json）
skill 目录下的 config.json 包含环境级配置，首次使用前确认 builder_dir 路径正确：
{
"builder_dir": "C:\\Users\\<user>\\.vscode\\extensions\\cl.eide-<version>\\res\\tools\\win32\\unify_builder",
"builder_exe": "unify_builder.exe",
"code_exe": "code",
"toolchain_prefix": "arm-none-eabi-",
"operation_mode": 1
}
builder_dir：EIDE unify_builder 所在目录（必填，位于 VS Code 扩展目录下）builder_exe：builder 可执行文件名，Windows 默认unify_builder.execode_exe：VS Code CLI 路径，默认从 PATH 查找codetoolchain_prefix：用于 size 分析的工具链前缀，默认arm-none-eabi-operation_mode：1直接执行 /2输出风险摘要但不阻塞 /3执行前确认
工程级配置（workspace/.embeddedskills/config.json）
工程级共享配置统一保存在工作区的 .embeddedskills/config.json 中：
{
"eide": {
"project": "",
"config": "",
"log_dir": ".embeddedskills/build"
}
}
project：默认 EIDE 工程根目录（包含.eide/eide.yml的目录），构建成功后会自动更新config：默认构建配置名称（对应 eide.yml 中的 ConfigName），构建成功后会自动更新log_dir：构建日志输出目录，默认.embeddedskills/build
参数解析优先级
参数解析顺序（从高到低）：
- CLI 显式参数
- 环境级配置（skill/config.json）
- 工程级配置（.embeddedskills/config.json）
.embeddedskills/state.json（上次构建记录）- 搜索/询问
子命令
| 子命令 | 用途 | 风险 |
|---|---|---|
scan |
搜索当前目录下的 EIDE 工程（含 .eide/eide.yml 的目录） |
低 |
configs |
枚举工程中的构建配置 | 低 |
build |
增量编译 | 中 |
rebuild |
全量重建 | 中 |
clean |
清理构建产物 | 高 |
size |
分析 ELF 文件大小（text/data/bss 和内存使用） | 低 |
执行流程
- 读取
config.json，确认builder_dir路径有效 - 未指定子命令时默认执行
scan - 未提供工程路径时先执行
scan搜索工程 - 同时发现多个工程或多个配置时，列出选项让用户选择，绝不自动猜测
build/rebuild/clean按operation_mode决定是否需要确认build/rebuild成功后，从构建目录解析elf_file/hex_file等产物路径- 所有构建命令基于
builder.params调用unify_builder，输出到日志文件后解析 size默认分析最近一次构建产物的 .elf 文件
脚本调用
skill 目录下有 Python 脚本，使用标准库 + PyYAML 实现。
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 191 lines · 151 tokens per session scan A e61c63b456a6
eide is a skill published in the GitHub repository zhinkgit/embeddedskills (756 stars, last pushed yesterday), licensed MIT. It adds 151 tokens to every session and 2,153 once invoked, about $0.0006 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-08-30.
Other skills, from other repositories
ros2-troubleshooting
Diagnose ROS 2 Jazzy faults that reading the code cannot settle: QoS mismatch, sensor-mount and frame errors (REP 103/105), and odometry calibrated against CAD instead of the floor. Ships four runnable pass/fail checks.
mastra-api
Interact with Mastra development server API for debugging agents, viewing conversation threads, listing/inspecting tools and workflows, accessing observability data, and managing Mastra resources. Use when working with Mastra agents and need to inspect runtime state, debug agent errors, view thread history, see…
gke-ai-troubleshooting-tpu-vbar-oom
Diagnoses and prevents vbarcontrolagent segfaults, out-of-memory (OOM) errors, and TPU device initialization failures on TPU v6e nodes in GKE caused by race conditions during TPU device resets or high-frequency metrics polling. Use when troubleshooting vbarcontrolagent crashes, memory cgroup OOMs in serial console…
diagnose-driver-install
Diagnose NVIDIA driver installation failures on DeepOps-managed nodes — nvidia-smi errors, "No devices were found", DKMS build failures, or GPU pods crash-looping. Use before reinstalling anything.
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
pyats-troubleshoot
Systematic network troubleshooting - connectivity, routing, interface, protocol, and performance issues using structured OSI-layer and divide-and-conquer methodology, via direct CLI/pyATS access. Use when something is broken, a device is unreachable, a link is flapping, users report slow performance, or an OSPF/BGP…