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/build-initgit 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-init)<a href="https://agentmods.dev/commands/jannleo/telinksdk-builder-mcp/build-init"><img src="https://agentmods.dev/badge/commands/jannleo/telinksdk-builder-mcp/build-init.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.00030 | $0.00453 |
| Opus 5 | $0.00015 | $0.00227 |
| Sonnet 5 | $0.00006 | $0.00091 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
build-init 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
使用生成器 ${COCO_PLUGIN_ROOT}/trae_build_init.py 为当前工作区 ${workspaceFolder} 生成 builder.json，使该仓库接入 trae-builder 构建体系。
用户参数 $ARGUMENTS：
- 默认（空）：扫描
${workspaceFolder}并生成builder.json。 - 若含
--ide <路径>：用该 IDE 路径覆盖检测到的默认值。
执行步骤：
- 用 Bash 工具运行：
python "${COCO_PLUGIN_ROOT}/trae_build_init.py" "${workspaceFolder}" $ARGUMENTS - 读取生成的
${workspaceFolder}\builder.json（用 Read 工具）。 - 向用户汇报：
- 检测器命中的模式（A-type release_sdk_tool / B-type telink_ble post-build / C-type eclipse-only / makefile / generic / fallback 模板）
- 构建脚本路径、解释器
- IDE 路径、芯片、默认构建目标
- 生成的预设列表
- 若是 fallback 模板（
build.script.path为REPLACE_WITH_BUILD_SCRIPT），明确告诉用户：未自动识别出构建脚本，需要手动编辑builder.json的build.script.path指向实际的构建脚本（.bat/.ps1/Makefile），并补全参数。 - 提醒用户：生成后即可用
/build info查看配置、/build <预设名>编译；如需调整，直接编辑builder.json。
注意：
${workspaceFolder}是当前工作区根目录。- 生成器会覆盖已存在的
builder.json；若已存在robin_builder.json会优先复用其内容并规范化。 - 不要自行编造构建脚本路径，一切以生成器输出为准。
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 · 28 lines · 30 tokens per session scan A a9dd57db365d
build-init is a command published in the GitHub repository JannLeo/telinksdk-builder-mcp (1 stars, last pushed 26d ago), licensed MIT. It adds 30 tokens to every session and 453 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.