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 skills add grasscaograss/AwesomeWeldoneSkills --skill robimweld-source-debuggit clone --depth 1 https://github.com/grasscaograss/AwesomeWeldoneSkillsWrote 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/grasscaograss/awesomeweldoneskills/robimweld-source-debug)<a href="https://agentmods.dev/skills/grasscaograss/awesomeweldoneskills/robimweld-source-debug"><img src="https://agentmods.dev/badge/skills/grasscaograss/awesomeweldoneskills/robimweld-source-debug.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.00171 | $0.03448 |
| Opus 5 | $0.00086 | $0.01724 |
| Sonnet 5 | $0.00034 | $0.00690 |
| Haiku 4.5 | $0.00017 | $0.00345 |
Grade A, and why
robimweld-source-debug 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 7d 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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RobimWeld 源码调试模式切换
操作型 skill，帮用户切换 UseRobimWeldSource 源码调试模式：写入/删除 Directory.Build.local.props、验证源码路径、跑 clean/restore/build。与 robimweld-release-check 联动——切之前先确认源码版本到位。
规则权威来源：README.md §"RobimWeld 调试模式"。本 skill enforce 而非重写这些规则。
三层调试能力
RobimWeld 调试分三层，本 skill 管 L3（L1/L2 见 README）：
| 层级 | 场景 | 机制 | 本 skill |
|---|---|---|---|
| L1 Source Link 只读单步 | 定位问题不改源码 | NuGet + snupkg + Source Link | 不管 |
| L2 源码项目浏览 | Rider 里展开源码项目 | WeldoneWithSource.slnx（主仓根，已提交） |
不管，但推荐配合 |
| L3 源码模式联调 | 改源码即改即生效 | UseRobimWeldSource=true + AdditionalProperties 级联 |
核心职责 |
关键：L2 只让项目"看得见"，L3 才"切得动"依赖。推荐用
WeldoneWithSource.slnx打开 Rider 的同时设local.props开 L3，两者互补。
模式机制
Directory.Build.props（主仓根，受版本管理）定义：
UseRobimWeldSource（默认false）RobimWeldAlgorithmSourceRoot（默认..\RobimWeld.Algorithm，即D:\RobimWeld.Algorithm）RobimWeldDevicesSourceRoot（默认..\RobimWeld.Devices，即D:\RobimWeld.Devices）
各 csproj 用 Condition="'$(UseRobimWeldSource)' == 'true'" 切换：
true→ProjectReference指向同级源码仓库的 csproj（可单步、改源码即生效）false→PackageReference走 NuGet 包（默认）
持久切换：在主仓根写 Directory.Build.local.props（已 gitignore）设 UseRobimWeldSource=true，被 Directory.Build.props 第 18 行的 <Import ... Condition="Exists(...)"> 加载。
单次切换（不落文件）：dotnet build WeldoneForCode.slnf -p:UseRobimWeldSource=true。
跨仓级联（为什么不能只靠 slnx）
源码切换是跨仓级联链，不传 AdditionalProperties 会导致源码与 NuGet 混用：
weldone 主仓 (拨 UseRobimWeldSource=true)
↓ ProjectReference + AdditionalProperties="$(RobimWeldSourceProjectProperties)"
RobimWeld.Devices 源码 (Devices.csproj/Vision.csproj 内部也有 Condition 分支)
↓ 自己切到源码分支
RobimWeld.Algorithm 源码 (终端，无需切换)
RobimWeldSourceProjectProperties = UseRobimWeldSource=true;RobimWeldAlgorithmSourceRoot=...;RobimWeldDevicesSourceRoot=...，通过 AdditionalProperties 注入 Devices 子构建。不传 → Devices 子项目走 NuGet 分支引 Algorithm 包 → 源码版 Devices + NuGet 版 Algorithm 混用 → 类型冲突 + 调试断链。
所以 WeldoneWithSource.slnx 只是"看得见"，UseRobimWeldSource 才是"切得动"——两者必须配合。
What ships with it
1 file 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.
- 7d ago First seen · 203 lines · 171 tokens per session scan A 3f3fd0b72b00
robimweld-source-debug is a skill published in the GitHub repository grasscaograss/AwesomeWeldoneSkills (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 171 tokens to every session and 3,448 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-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.