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 serejaris/kimi-skills --skill glab-workitemsgit clone --depth 1 https://github.com/serejaris/kimi-skillsWrote 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/serejaris/kimi-skills/glab-workitems)<a href="https://agentmods.dev/skills/serejaris/kimi-skills/glab-workitems"><img src="https://agentmods.dev/badge/skills/serejaris/kimi-skills/glab-workitems/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/serejaris/kimi-skills/glab-workitems"><img src="https://agentmods.dev/badge/skills/serejaris/kimi-skills/glab-workitems.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.00062 | $0.00982 |
| Opus 5 | $0.00031 | $0.00491 |
| Sonnet 5 | $0.00012 | $0.00196 |
| Haiku 4.5 | $0.00006 | $0.00098 |
Grade A, and why
glab-workitems 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 9d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
glab workitems
列出和管理 GitLab 工作项——GitLab 中新一代的工作跟踪格式,支持任务(Task)、OKR、关键结果(Key Result)、史诗(Epic)等类型。
glab v1.87.0 新增
什么是工作项?
工作项是 GitLab 的统一工作跟踪模型。它们在传统 Issue 的基础上扩展,支持:
- 任务(Task) — Issue 内的子任务
- OKR — 目标与关键结果
- 关键结果(Key Result) — 与 OKR 关联的可衡量成果
- 史诗(Epic,新一代) — 跨里程碑的大型工作单元
- 事件(Incident) — 关联到事件管理
快速入门
# 列出当前项目的工作项
glab workitems list
# 列出指定项目的工作项
glab workitems list --repo owner/project
# 以 JSON 格式输出
glab workitems list --output json
常见工作流
列出工作项
# 所有工作项(默认:打开状态)
glab workitems list
# 按类型筛选
glab workitems list --type Task
glab workitems list --type OKR
glab workitems list --type KeyResult
glab workitems list --type Epic
# 按状态筛选
glab workitems list --state opened
glab workitems list --state closed
# 以 JSON 格式输出(便于脚本处理)
glab workitems list --output json | python3 -c "
import sys, json
items = json.load(sys.stdin)
for item in items:
print(f\"{item['iid']}: {item['title']} [{item['type']}]\")
"
指定仓库或群组
# 指定仓库
glab workitems list --repo mygroup/myproject
# 群组级别的工作项
glab workitems list --group mygroup
工作项 vs Issue
| 功能 | Issue | 工作项 |
|---|---|---|
| 标准缺陷/功能跟踪 | ✅ | ✅ |
| 任务(子任务) | ❌ | ✅ |
| OKR / 关键结果 | ❌ | ✅ |
| 新一代史诗 | ❌ | ✅ |
| CLI 支持 | 完整 | list(v1.87.0) |
标准 Issue 工作流请使用 glab issue。处理任务、OKR 或新一代史诗时请使用 glab workitems。
故障排查
"workitems: command not found":
- 需要 glab v1.87.0 或更高版本。使用
glab version检查。
预期有结果但返回为空:
- 工作项与 Issue 是不同的类型。以 Issue 方式创建的条目不会出现在这里,除非已被转换。
- 在 GitLab 界面中查看项目的"计划 > 工作项"侧边栏。
类型筛选无结果:
- 并非所有 GitLab 实例都启用了全部工作项类型。GitLab SaaS 比私有部署实例支持更多类型。
相关技能
glab-issue— 标准 Issue 管理glab-milestone— 里程碑(常与 OKR 配合使用)glab-iteration— 迭代/冲刺管理glab-incident— 事件管理(一种工作项类型)
命令参考
glab workitems list [--flags]
Flags:
--group Select a group/subgroup
--output Format output as: text, json
--page Page number
--per-page Number of items per page
--repo Select a repository
--state Filter by state: opened, closed, all
--type Filter by work item type
-h, --help Show help
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.
- 9d ago First seen · 117 lines · 62 tokens per session scan A cd84e70ca7ef
glab-workitems is a skill published in the GitHub repository serejaris/kimi-skills (6 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 982 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
syndic
Gère un parc de copropriétés en France avec vue portfolio consolidée. Couvre administration, comptabilité (décret 2005, plan comptable copro, 5 annexes), assemblées générales (convocation, PV, notification), appels de fonds, travaux, fournisseurs, recouvrement d'impayés et transition de syndic. Maîtrise les majorités…
implement-improvements
Validate improvements from .turbo/improvements.md, recommend a working set tailored to what's in the backlog, and run one lane: direct fixes, investigation, or planned work. One lane per session. Use when the user asks to "implement improvements", "work on improvements", "address improvements", "process improvement…
note-improvement
Capture an out-of-scope improvement opportunity so it doesn't get lost. Use when the user asks to "note improvement", "save improvement", "track this for later", "remember this improvement", "note this idea", "log improvement", "backlog this", or "park this idea". Also invoke proactively when noticing something…
create-issue
Create a GitHub issue with a drafted title and body. Use when the user asks to "create an issue", "file an issue", "open an issue", "submit an issue", "report a bug", "file a bug report", "file a feature request", or "file a design proposal".
pick-next-issue
Fetch and rank open GitHub issues by community engagement, present the top 3 candidates, and plan implementation for the selected issue. Use when the user asks to "pick next issue", "next issue", "which issue should I work on", "top issues", "most popular issues", "prioritize issues", or "what should I work on next".
split-and-ship
Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".