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 skills/zhinkgit/embeddedskills/probe-rsnpx skills add zhinkgit/embeddedskills --skill probe-rsgit 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/probe-rs)<a href="https://agentmods.dev/skills/zhinkgit/embeddedskills/probe-rs"><img src="https://agentmods.dev/badge/skills/zhinkgit/embeddedskills/probe-rs.svg" alt="Measured on agentmods" 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 | $0.00182 | $0.01411 |
| Opus 5 | $0.00091 | $0.00705 |
| Sonnet 5 | $0.00036 | $0.00282 |
| Haiku 4.5 | $0.00018 | $0.00141 |
Grade A, and why
probe-rs 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 4d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
probe-rs 下载与调试
本 skill 提供 probe-rs CLI 的结构化包装，覆盖探针发现、目标信息、烧录、复位、内存读写、one-shot GDB 调试和 RTT 日志读取。
Windows 下优先使用 py -3 调用脚本；若 arm-none-eabi-gdb 已在 PATH 中，gdb 子命令可自动发现，不强依赖 skill config.json。
配置
环境级配置（skill/config.json）
首次使用前建议在 skill 目录下创建 config.json：
{
"exe": "probe-rs",
"gdb_exe": "C:\\Program Files\\Arm\\GNU Toolchain mingw-w64-x86_64-arm-none-eabi\\bin\\arm-none-eabi-gdb.exe",
"gdb_port": 3333,
"dap_port": 50000,
"operation_mode": 1
}
exe：probe-rs可执行文件路径或命令名gdb_exe：arm-none-eabi-gdb路径，gdb子命令需要gdb_port：默认 GDB 端口dap_port：预留给交互式 DAP 会话operation_mode：1直接执行 /2输出风险摘要但不阻塞 /3执行前确认
工程级配置（.embeddedskills/config.json）
{
"probe-rs": {
"chip": "STM32F407VGTx",
"protocol": "swd",
"probe": "",
"speed": 4000,
"connect_under_reset": false
}
}
chip：芯片型号，probe-rs主后端必填protocol：swd或jtagprobe：探针选择器，格式VID:PID[:Serial]speed：调试速率 kHzconnect_under_reset：连接时是否保持 reset
参数优先级：CLI 参数 > 工程配置（.embeddedskills/config.json）> state.json > skill 配置（config.json）> 默认值
各层职责：skill config.json 提供工具路径与端口等环境级常量；.embeddedskills/config.json 提供芯片、协议等工程级参数；CLI 参数在单次调用中覆盖一切。
子命令
| 子命令 | 用途 | 风险 |
|---|---|---|
list |
枚举可用探针 | 低 |
info |
查看探针与目标信息 | 低 |
flash |
烧录固件（elf/hex/bin/uf2） | 高 |
erase |
擦除芯片非易失存储 | 高 |
reset |
复位目标芯片 | 高 |
read-mem |
读取内存 | 低 |
write-mem |
写内存 | 高 |
attach / run |
包装 probe-rs attach/run | 低 |
gdb |
启动 GDB Server 并执行 one-shot 调试 | 低 |
rtt |
读取 RTT 日志 | 低 |
典型调用
# 列出探针
py -3 <skill-dir>/scripts/probe_rs_exec.py list --json
# 烧录 ELF
py -3 <skill-dir>/scripts/probe_rs_exec.py flash --chip STM32F407VGTx --file build/app.elf --json
# 烧录 BIN（必须提供地址）
py -3 <skill-dir>/scripts/probe_rs_exec.py flash --chip STM32F407VGTx --file build/app.bin --address 0x08000000 --json
# 读取内存
py -3 <skill-dir>/scripts/probe_rs_exec.py read-mem --chip STM32F407VGTx --address 0x20000000 --length 16 --width b32 --json
# one-shot backtrace
py -3 <skill-dir>/scripts/probe_rs_gdb.py backtrace --chip STM32F407VGTx --elf build/app.elf --json
# RTT
py -3 <skill-dir>/scripts/probe_rs_rtt.py --chip STM32F407VGTx --json
What ships with it
7 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.
- 4d ago First seen · 107 lines · 182 tokens per session scan A 11e9b6a54766
probe-rs is a skill published in the GitHub repository zhinkgit/embeddedskills (620 stars, last pushed yesterday), licensed MIT. It adds 182 tokens to every session and 1,411 once invoked, about $0.0009 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-30.
Other skills, from other repositories
browser-qa
Use when you need lightweight browser QA for a web page, local HTML file, or app: inspect console errors, broken assets, keyboard/focus behavior, viewport readability, and publish evidence-backed findings JSON through a local HTML report viewer.
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…
create-mermaid-diagrams
Create, validate, and repair Mermaid diagrams for technical documentation with a deterministic CLI feedback loop. Use when an AI needs to create Mermaid diagrams, improve Mermaid diagram quality, validate Mermaid fences in markdown, diagnose Mermaid rendering failures, or fix Mermaid syntax and formatting issues.
create-pull-request
Generate a reviewer-ready pull request or merge request title and description from branch changes. Use when a user asks to draft PR/MR content, summarize branch deltas against a base branch, or optionally create the PR with gh/glab after approval.
tilt-dev
Manage local development environments with Tilt. Use when working with projects that run services via Tilt (indicated by presence of Tiltfile), including checking service status, viewing logs, troubleshooting connectivity issues, or managing the Tilt stack. Essential for projects using Tiltfile with localresource for…
uv-usage
Provides concise guidance for using uv (Python package manager), including project workflows, pip-compatible commands, Python version management, and PEP 723 inline script dependencies. Use when users mention uv, uv run, inline dependencies, PEP 723, or Python dependency/project management.