A command-line tool wrapper for probe-rs, which connects a computer to a microcontroller through a hardware debug probe. It supports common firmware programming and debugging operations over SWD or JTAG.

Use it to find probes, identify chips, program firmware, reset targets, read or write memory, run one-shot GDB sessions, and collect RTT logs.

It groups probe discovery, chip information, flashing, reset, memory access, GDB debugging, and RTT log reading into structured commands. This reduces manual command setup when working with supported embedded targets.

probe-rs — Skill for Claude Code by zhinkgit/embeddedskills

Install

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.

Any agent

npx skills add zhinkgit/embeddedskills --skill probe-rs

Clone the repo

git clone --depth 1 https://github.com/zhinkgit/embeddedskills

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/zhinkgit/embeddedskills/probe-rs/github.svg)](https://agentmods.dev/skills/zhinkgit/embeddedskills/probe-rs)

Your own site

<a href="https://agentmods.dev/skills/zhinkgit/embeddedskills/probe-rs"><img src="https://agentmods.dev/badge/skills/zhinkgit/embeddedskills/probe-rs/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/zhinkgit/embeddedskills/probe-rs"><img src="https://agentmods.dev/badge/skills/zhinkgit/embeddedskills/probe-rs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 182 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,411 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

Socket pass 15 Sept 2026
Snyk pass 15 Sept 2026
NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00182	$0.01411
Opus 5.5	$0.00073	$0.00564
Sonnet 5.5	$0.00036	$0.00282
Haiku 4.5	$0.00018	$0.00141

Measured 1mo ago against content hash 11e9b6a54766, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo ago.

The scan reads SKILL.md. This mod also ships 6 executable files (scripts/probe_rs_exec.py, scripts/probe_rs_gdb_common.py, scripts/probe_rs_gdb.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

probe-rs/SKILL.md · 107 lines

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 或 jtag
probe：探针选择器，格式 VID:PID[:Serial]
speed：调试速率 kHz
connect_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

Read the full file on GitHub · 107 lines

Files

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.

Changes

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 · 107 lines · 182 tokens per session scan A 11e9b6a54766

Subscribe to this mod's changes

probe-rs is a skill published in the GitHub repository zhinkgit/embeddedskills (756 stars, last pushed yesterday), licensed MIT. It adds 182 tokens to every session and 1,411 once invoked, about $0.0007 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.

Debugging ai-coding-assistant automation can-bus can-fd devtools

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…

liatrio-labs/ai-prompts · 80 tokens

d3k

Use when the user asks to use d3k, run/dev/test/debug a web project with d3k, or reproduce a browser issue. Own the runtime: reuse or background-start d3k non-interactively, wait for readiness, use its project-stable managed Chrome profile, and inspect unified browser/server evidence.

vercel-labs/dev3000 · 68 tokens

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…

asheshgoplani/agent-deck · 86 tokens

devtools-bidirectional

Two-way event patterns between devtools panel and application. App-to-devtools observation, devtools-to-app commands, time-travel debugging with snapshots and revert. structuredClone for snapshot safety, distinct event suffixes for observation vs commands, serializable payloads only.

TanStack/devtools · 59 tokens

devtools-instrumentation

Analyze library codebase for critical architecture and debugging points, add strategic event emissions. Identify middleware boundaries, state transitions, lifecycle hooks. Consolidate events (1 not 15), debounce high-frequency updates, DRY shared payload fields, guard emit() for production. Transparent server/client…

TanStack/devtools · 64 tokens

deck-repro

Reproduce agent-deck bugs from an issue, transcript excerpt, or description in an isolated environment, and prove fixes with the same reproduction and a regression test. Use for a concrete agent-deck issue or candidate, verifying a fix, preparing a contributor bug-fix PR, or when deck-retro passes a candidate. Broad…

asheshgoplani/agent-deck · 108 tokens