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/JannLeo/telinksdk-builder-mcpWrote 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/commands/jannleo/telinksdk-builder-mcp/serial)<a href="https://agentmods.dev/commands/jannleo/telinksdk-builder-mcp/serial"><img src="https://agentmods.dev/badge/commands/jannleo/telinksdk-builder-mcp/serial/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/commands/jannleo/telinksdk-builder-mcp/serial"><img src="https://agentmods.dev/badge/commands/jannleo/telinksdk-builder-mcp/serial.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.00021 | $0.00446 |
| Opus 5.5 | $0.00008 | $0.00178 |
| Sonnet 5.5 | $0.00004 | $0.00089 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
serial 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 2mo 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.
What it actually says
使用通用构建运行器 ${COCO_PLUGIN_ROOT}/trae_build_runner.py 的 serial 子命令，抓取串口日志用于验证烧录后固件行为（构成"编译→烧录→看串口"闭环）。需 pyserial。
调用
# 列出可用串口
python "${COCO_PLUGIN_ROOT}/trae_build_runner.py" --project "${workspaceFolder}" serial list
# 抓取串口（端口/波特率默认从 builder.json serial 段读，否则自动选第一个端口 + 115200）
python "${COCO_PLUGIN_ROOT}/trae_build_runner.py" --project "${workspaceFolder}" serial capture --port COM3 --baud 115200 --duration 5 --max-lines 200
选项速查（capture）
| 选项 | 说明 |
|---|---|
--port |
串口（COM3 / /dev/ttyUSB0）；空=配置默认或自动检测 |
--baud |
波特率；空=配置默认(115200) |
--duration |
抓取时长秒数（默认 5.0） |
--max-lines |
最大行数（默认 200） |
汇报规范
解析 JSON 后向用户汇报：
- list：端口数组（port、description），建议用户选哪个
- capture：抓到的行数、前若干行日志摘要；若日志含 "boot ok" / 版本号 / 预期关键字则提示固件正常，否则把日志交给用户判断
完整闭环
用户说"编译并烧录看效果"时，依次：/build → /flash wf → /serial capture，把串口日志给用户判断固件行为。
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.
- 2mo ago First seen · 36 lines · 21 tokens per session scan A 6f9d19ea64d6
serial is a command published in the GitHub repository JannLeo/telinksdk-builder-mcp (1 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 446 once invoked, about $0.0001 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-31.
Other commands, from other repositories
ee-review
Produce an EE decision document (escalating intervention ladder + binding constraints, cited and confidence-graded) for an analog/placement-blocked board.
cortex-m
Generate Cortex-M startup code or a linker script, configure a core subsystem, decode a fault, or add DWT timing.
debug-embedded
Attach a debugger, halt and inspect a target, decode fault registers, or configure ITM, SWO, or ETM trace.
gpu
Diagnose GPU health, discover bounded recipes, and collect typed numeric evidence without guessing from screenshots.
debug
A command-line debugging toolkit for embedded programs using J-Link or OpenOCD, tools that connect a computer to a microcontroller for inspection.
la
A command for capturing and decoding signals with a Saleae logic analyzer, a device that records electrical digital signals over time. It supports buses such as UART, SPI, and I2C, which are common ways chips communicate with peripherals.