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-release-checkgit 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-release-check)<a href="https://agentmods.dev/skills/grasscaograss/awesomeweldoneskills/robimweld-release-check"><img src="https://agentmods.dev/badge/skills/grasscaograss/awesomeweldoneskills/robimweld-release-check/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/robimweld-release-check"><img src="https://agentmods.dev/badge/skills/grasscaograss/awesomeweldoneskills/robimweld-release-check.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.00164 | $0.02779 |
| Opus 5 | $0.00082 | $0.01389 |
| Sonnet 5 | $0.00033 | $0.00556 |
| Haiku 4.5 | $0.00016 | $0.00278 |
Grade A, and why
robimweld-release-check scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
fallback 用 PackageBaseAddress（curl，包名小写）： How it starts
The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RobimWeld 发布一致性校验
校验 RobimWeld.Algorithm 与 RobimWeld.Devices 两个私有仓库的 NuGet 包发布状态，定位"代码已合并、版本号已改、但没发包"这类问题，并在确认后打 tag 触发 CI 发包。
规则权威来源：README.md §"包版本与发布顺序"（196-202 行）。本 skill enforce 而非重写这些规则。
两条版本线
| 版本线 | 主仓分支 | 源仓库分支 | tag 前缀 |
|---|---|---|---|
| 护圈龙门 v1.x | feature/merge护圈龙门-nuget |
master |
v1.0.x（Algorithm）/ v1.1.x（Devices） |
| Kuka 悬臂 v2.x-alpha | feature/kuka-nuget-2.0 |
kuka |
v2.0.x-alpha |
判定版本线：读主仓当前分支名，匹配上表。无法匹配时停止并询问用户当前属于哪条线。
仓库 → 产出包映射
| 源仓库 | 本地路径 | 产出包 |
|---|---|---|
RobimWeld.Algorithm |
D:\RobimWeld.Algorithm（WSL /mnt/d/RobimWeld.Algorithm） |
RobimWeld.Algorithm.Weld、RobimWeld.Data.Weld |
RobimWeld.Devices |
D:\RobimWeld.Devices（WSL /mnt/d/RobimWeld.Devices） |
RobimWeld.Devices、RobimWeld.Devices.Robot、RobimWeld.Devices.Vision、RobimWeld.Scanning.Contracts |
git 地址：[email protected]:robimweld/RobimWeld.Algorithm.git、[email protected]:robimweld/RobimWeld.Devices.git。
版本号读取规则
两条线的版本号存放位置不同，必须都覆盖：
Kuka v2.x-alpha 线
两个仓库均在 Directory.Build.props 用单一字段：
- Algorithm：
<Version>2.0.x-alpha</Version> - Devices：
<RobimWeldPackageVersion>2.0.x-alpha</RobimWeldPackageVersion>+<Version>$(RobimWeldPackageVersion)</Version>
读取 Directory.Build.props 一个文件即可。
护圈龙门 v1.x 线
- Algorithm：
Directory.Build.props无<Version>字段（1.x 早期）；版本号写在各 csproj 的<Version>。必须遍历src/**/*.csproj取所有<Version>值并集校验同号。 - Devices：
Directory.Build.props单一<Version>1.1.x</Version>，一个文件即可。
一致性硬规则
仓库内同号（强制）
同一仓库产出的所有包，版本号必须一致。
违反示例：护圈龙门线 v1.0.6 tag 时，Algorithm 仓库 RobimWeld.Algorithm.Weld.csproj = 1.0.5、RobimWeld.Data.Weld.csproj = 1.0.6 → 仓库内不同号 → 阻断发版，提示先修版本号。
跨仓库可不同（允许）
护圈龙门线 Algorithm = 1.0.x / Devices = 1.1.x 合法，不校验跨仓库。
主仓引用 vs 源仓库 tag
主仓 Directory.Packages.props 引用的版本，必须在对应源仓库已打 tag，且 tag 指向的 commit 包含该版本号。否则判定"代码合并了但没发包"。
CI 触发机制
两个仓库 .gitlab-ci.yml 均为：
publish:
rules:
- if: $CI_COMMIT_TAG # 只有 tag 推送才发包
分支推送只 build，不 publish。漏打 tag = 没发包，这是最常见的问题根因。
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.
- 12d ago First seen · 168 lines · 164 tokens per session scan A 5f3eb89ec3a4
robimweld-release-check is a skill published in the GitHub repository grasscaograss/AwesomeWeldoneSkills (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 164 tokens to every session and 2,779 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. (gstack).
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
releasepr
Adopt, configure, run, or troubleshoot compozy/releasepr in a consuming repository, including Actions, beta/stable/legacy plans, notes, dry-runs, and publication. Excludes pr-release internals and general versioning advice.
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…
seed-snapshot-release
An automated workflow for creating and tracking a snapshot release of the pull request on the current branch. A snapshot release is a temporary package build used for testing a branch before a normal release.