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 skills/grasscaograss/awesomeweldoneskills/gitlab-opsnpx skills add grasscaograss/AwesomeWeldoneSkills --skill gitlab-opsgit 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/gitlab-ops)<a href="https://agentmods.dev/skills/grasscaograss/awesomeweldoneskills/gitlab-ops"><img src="https://agentmods.dev/badge/skills/grasscaograss/awesomeweldoneskills/gitlab-ops.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.00084 | $0.01381 |
| Opus 5 | $0.00042 | $0.00691 |
| Sonnet 5 | $0.00017 | $0.00276 |
| Haiku 4.5 | $0.00008 | $0.00138 |
Grade A, and why
gitlab-ops 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 6d 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.
使用 pwsh 7（默认 UTF-8；curl 在 Windows 中文编码有问题）： How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitLab 项目操作
Weldone 项目的 GitLab 实例信息：
| 配置项 | 值 |
|---|---|
| URL | http://gitlab.roboticplus.com:2022 |
| Project ID | 305 |
| API Base | http://gitlab.roboticplus.com:2022/api/v4/projects/305 |
Token 获取：从用户获取，或读取环境变量 $env:GITLAB_TOKEN。
API 调用方式
使用 pwsh 7（默认 UTF-8；curl 在 Windows 中文编码有问题）：
$Headers = @{ "PRIVATE-TOKEN" = $env:GITLAB_TOKEN; "Content-Type" = "application/json" }
$Base = "http://gitlab.roboticplus.com:2022/api/v4/projects/305"
或使用 Python（本环境有 python 可用）。
标签体系
项目使用 维度::内容 格式的 scoped labels，共 5 个维度 30 个标签：
| 维度 | 色系 | 值 |
|---|---|---|
| 类型（蓝） | #2E86C1 |
缺陷、功能、优化、重构、杂务 |
| 优先级（红） | #C0392B |
紧急、高、中、低 |
| 阶段（绿） | #27AE60 |
待办、开发中、审查中、待测试、测试通过、已完成 |
| 模块（紫） | #8E44AD |
焊缝规划、焊接模板、粗定位、精定位、扫描校准、机器人控制、双臂协同、状态机、前端、插件、基础设施、产能统计 |
| 状态（黄） | #F1C40F |
阻塞、需要讨论、搁置、不做 |
| 规则：每个 Issue 必须有 类型 + 优先级 + 模块。阶段标签互斥（同一时间只有一个）。 |
CI 自动化（阶段流转）
MR 创建 → 阶段::待测试，测试通过后手动设 阶段::测试通过，MR 合并到 develop → 阶段::已完成。详见 .gitlab-ci.yml 中的 label-on-mr 和 label-on-merge job。脚本位于 scripts/gitlab-label-on-merge.ps1。
常用操作
创建 Issue
使用 gitlab-issue skill（对话式引导创建，自动推断标签）。用户说"建个 issue"时优先触发该 skill。
网页端兜底：.gitlab/issue_templates/ 下有 Bug缺陷报告、功能请求、优化建议三个模板。
查询 Issue
# 按标签查询
GET /issues?labels=类型::缺陷,模块::粗定位&state=opened
# 按关键词搜索
GET /issues?search=关键词
# 获取单个 Issue
GET /issues/{iid}
# 获取 Issue 评论
GET /issues/{iid}/notes
创建 Issue
POST /issues
{
"title": "标题",
"description": "描述（支持 Markdown）",
"labels": "类型::功能,优先级::中,模块::焊缝规划,阶段::待办",
"assignee_ids": [用户ID]
}
创建后务必打齐 3 个必选标签（类型 + 优先级 + 模块）。
更新 Issue
PUT /issues/{iid}
{
"labels": "类型::缺陷,优先级::高,模块::粗定位,阶段::开发中",
"state_event": "close" # 关闭 Issue
}
标签管理
# 列出所有标签
GET /labels
# 创建标签
POST /labels
{ "name": "维度::内容", "color": "#HEX", "description": "说明" }
# 删除标签
DELETE /labels/{name} # name 需要 URL encode
# 替换 Issue 标签时，先加新再删旧（或用 PUT issues/{iid} 的 labels 字段直接替换）
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.
- 6d ago First seen · 155 lines · 84 tokens per session scan A b195123c496c
gitlab-ops is a skill published in the GitHub repository grasscaograss/AwesomeWeldoneSkills (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 84 tokens to every session and 1,381 once invoked, about $0.0004 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
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…