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 commands/jannleo/telinksdk-builder-mcp/buildgit 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/build)<a href="https://agentmods.dev/commands/jannleo/telinksdk-builder-mcp/build"><img src="https://agentmods.dev/badge/commands/jannleo/telinksdk-builder-mcp/build.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.1 | $0.00031 | $0.00703 |
| Opus 5 | $0.00015 | $0.00351 |
| Sonnet 5 | $0.00006 | $0.00141 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
build 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 5d 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
使用通用构建运行器处理当前工作区 ${workspaceFolder} 的 SDK 仓库（其根目录需含 builder.json 或 robin_builder.json）。
调用 ${COCO_PLUGIN_ROOT}/trae_build_runner.py 完成实际编译，不要自己拼命令。根据用户参数 $ARGUMENTS 选择子命令：
- 若参数为空或以
info开头：执行info子命令，展示该仓库的构建配置（参数、预设、产物配置）。 - 若参数以
list开头：执行list子命令，列出已收集的构建产物。 - 若参数以
build开头：把$ARGUMENTS里build之后的剩余内容原样作为子命令参数传给 runner（支持--preset <名称>、--param 键=值、--timeout 秒数、--dry-run）。 - 若参数以非上述关键字开头（如
rx_default）：视为预设名，执行build --preset <第一个参数>，其后的参数继续透传。
runner 路径固定为：${COCO_PLUGIN_ROOT}/trae_build_runner.py
项目路径用 --project "${workspaceFolder}"。
请按上述规则构造一条 python 命令并用 Bash 工具执行，然后把 runner 的 JSON 输出解析后向用户汇报：
- 编译是否成功（status 字段）
- 产物路径和大小（artifacts 数组）
- 若 dry_run，展示将要执行的完整命令
- 若失败，展示 exit_code 和日志路径
下面是 runner 用法速查（供你构造命令参考）：
python "${COCO_PLUGIN_ROOT}/trae_build_runner.py" --project "<项目路径>" info
python "${COCO_PLUGIN_ROOT}/trae_build_runner.py" --project "<项目路径>" list
python "${COCO_PLUGIN_ROOT}/trae_build_runner.py" --project "<项目路径>" build --preset <名称> [--param 键=值 ...] [--timeout 秒] [--dry-run]
烧录与串口
用户说"烧录/flash/下载固件""复位""抓串口看效果"时，用 /flash 或 /serial 命令（详见对应命令文档）。runner 也支持 flash 和 serial 子命令：
python "${COCO_PLUGIN_ROOT}/trae_build_runner.py" --project "<项目路径>" flash --command wf [--chip ...] [--input ...] [--verify] [--retry 3] [--pre-check] [--dry-run]
python "${COCO_PLUGIN_ROOT}/trae_build_runner.py" --project "<项目路径>" serial capture --port COM3 --duration 5
注意：$ARGUMENTS 为用户在 /build 后输入的全部参数。请正确拆分出子命令与透传部分。
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.
- 5d ago First seen · 42 lines · 31 tokens per session scan A 6a897446ca7d
build is a command published in the GitHub repository JannLeo/telinksdk-builder-mcp (1 stars, last pushed 26d ago), licensed MIT. It adds 31 tokens to every session and 703 once invoked, about $0.0002 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.