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 weldone-wsg-merge-domain-knowledgegit 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/weldone-wsg-merge-domain-knowledge)<a href="https://agentmods.dev/skills/grasscaograss/awesomeweldoneskills/weldone-wsg-merge-domain-knowledge"><img src="https://agentmods.dev/badge/skills/grasscaograss/awesomeweldoneskills/weldone-wsg-merge-domain-knowledge/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/skills/grasscaograss/awesomeweldoneskills/weldone-wsg-merge-domain-knowledge"><img src="https://agentmods.dev/badge/skills/grasscaograss/awesomeweldoneskills/weldone-wsg-merge-domain-knowledge.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.00105 | $0.03484 |
| Opus 5 | $0.00053 | $0.01742 |
| Sonnet 5 | $0.00021 | $0.00697 |
| Haiku 4.5 | $0.00011 | $0.00348 |
Grade A, and why
weldone-wsg-merge-domain-knowledge 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 12d 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 — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WeldSeamGroup 合并领域知识
1. 设计背景
FlexBeam 对称打断场景下，双机各需焊接多条 WSG。状态机 WeldSeamPairContext 原先硬编码 Robot0/Robot1 各一条，GetDualArmWsgPair 要求恰好 2 个。为支持 N:M 双机焊接，引入 双层表示 + 合并 WSG 方案。
核心约束
- 合并后模板只有一组起弧/收弧安全点
- 精定位映射必须分段计算（曲线+直线+曲线场景，全局 MapMatrix 精度不够）
- 前端零耦合（前端基于任意长度 GUID 列表）
- 状态机拓扑不改（仍以包角对为单位）
2. 双层表示
| 层级 | 位置 | 内容 | 消费者 |
|---|---|---|---|
| 原始 WSG | wp.WeldSeamGroups |
几何、扫描、CilIdx 映射 | VisionCaptureManager, CapturePointManager, MapMatrix |
| 合并 WSG | WrapPairsDict / WsgDicts |
模板、焊接规划、执行 | WeldPlanAppService, WeldPoseSolverManager, WeldExecute |
关键规则：wp.WeldSeamGroups 始终保留原始 WSG，不被合并替换。合并 WSG 仅存在于工艺列表字典中。
通过 MergedSources 建立双向引用，信息零损失。
3. 数据结构
3.1 MergedWsgSource
文件: src/Weldone.Domain/WeldProcedure/Procedure/Entities/WeldSeamGroup.cs
public class MergedWsgSource
{
public Guid OriginalWsgId { get; init; } // 原始 WSG Id
public int CilIdx { get; init; } // 原始 CilIdx（C++ 算法用的索引）
public int Order { get; init; } // 在合并路径中的顺序（0=最前）
public int VertexOffset { get; init; } // 该段在合并 WeldSeams 中的起始顶点索引
public int VertexCount { get; init; } // 该段的顶点数量
}
3.2 WeldSeamGroup.MergedSources
// 非空 → 本 WSG 由多个原始 WSG 合并而成
// 为空/null → 本 WSG 是原始 WSG
public List<MergedWsgSource>? MergedSources { get; set; }
判断是否合并 WSG：wsg.MergedSources != null && wsg.MergedSources.Count > 1
3.3 WeldSeamExecutionContext.OriginalWsgIds
文件: src/Weldone.Application.Contracts/Workflows/ScanWeldWorkflowData.cs
public List<Guid> OriginalWsgIds { get; set; } = new();
扫描阶段逐个处理原始 WSG，焊接阶段使用合并 WSG。为空时直接使用 WsgId。
4. MergeWsgs 合并规则
方法签名: WeldSeamGroup.MergeWsgs(IReadOnlyList<WeldSeamGroup> ordered, Guid newId)
| 属性 | 取值来源 |
|---|---|
| Type / Direction / Position / Feature / Shape | 第一个 WSG |
| IsClosed | false |
| TemplateDimensionKey | 第一个 WSG |
| WeldLegHeight / BevelType / BevelHeight / BevelDepth / GapWidth / BluntEdgeLength | 第一个 WSG |
| IsDefaultOrientation / TrackingMode / IsTrackingModeCustomized | 第一个 WSG |
| StartEdgeInfo | 第一个 WSG 的 StartEdgeInfo |
| EndEdgeInfo | 最后一个 WSG 的 EndEdgeInfo |
| WeldSeams | 所有原始 WSG 的 WeldSeams 拼接（每条 deep clone，新 GUID） |
| CilIdx | 第一个 WSG 的 CilIdx（用于模板匹配和 PathItems 索引） |
| MergedSources | 各原始 WSG 的 Id/CilIdx/Order/VertexOffset/VertexCount |
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.
- 12d ago First seen · 283 lines · 105 tokens per session scan A 4faa3aeac8c2
weldone-wsg-merge-domain-knowledge is a skill published in the GitHub repository grasscaograss/AwesomeWeldoneSkills (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 105 tokens to every session and 3,484 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…