glab-workitems

glab-workitems is a skill for Claude Code, Codex from vince-winkintel/gitlab-cli-skills. It costs 80 tokens per session (2,028 once invoked), scanned A, original, MIT.

A command-line skill for managing GitLab work items, GitLab's broader planning records for tasks, OKRs, key results, epics, incidents, and test cases.

In plain words
What is it for?
It helps create, list, update, and delete work items, including group-level epics and descriptions supplied from files.
Why use it?
It lets an agent handle these planning records directly instead of treating every item as a standard issue. The feature is marked experimental, so its commands may change.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It helps create, list, update, and delete work items, including group-level epics and descriptions supplied from files.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vince-winkintel/gitlab-cli-skills/glab-workitems
Install

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.

Any agent
npx skills add vince-winkintel/gitlab-cli-skills --skill glab-workitems
Clone the repo
git clone --depth 1 https://github.com/vince-winkintel/gitlab-cli-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for glab-workitems

README.md
[![agentmods](https://agentmods.dev/badge/skills/vince-winkintel/gitlab-cli-skills/glab-workitems/github.svg)](https://agentmods.dev/skills/vince-winkintel/gitlab-cli-skills/glab-workitems)
Your own site
<a href="https://agentmods.dev/skills/vince-winkintel/gitlab-cli-skills/glab-workitems"><img src="https://agentmods.dev/badge/skills/vince-winkintel/gitlab-cli-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.

agentmods 80×15 button for glab-workitems

Your own site · 80×15
<a href="https://agentmods.dev/skills/vince-winkintel/gitlab-cli-skills/glab-workitems"><img src="https://agentmods.dev/badge/skills/vince-winkintel/gitlab-cli-skills/glab-workitems.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,028 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00080 $0.02028
Opus 5.5 $0.00032 $0.00811
Sonnet 5.5 $0.00016 $0.00406
Haiku 4.5 $0.00008 $0.00203

Measured 9d ago against content hash 68c8185953d6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

glab-workitems/SKILL.md · 231 lines

How it starts

The opening of the file, as written. The whole thing — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.

glab work-items

Create, list, and delete GitLab work items — GitLab's unified work tracking model for tasks, OKRs, key results, epics, incidents, test cases, and related planning objects.

Assign an iteration

Use the numeric iteration ID with --iteration on create or update:

glab work-items create --type issue --title "Add feature" --iteration 123
glab work-items update 42 --iteration 123

Omitting the flag leaves the iteration unset on create and unchanged on update. Verify the work item's scope and the intended iteration before the write; do not substitute an iteration title for the ID.

⚠️ Experimental Feature

glab work-items is still marked EXPERIMENTAL upstream:

  • command shape may still change
  • availability can differ by GitLab version / feature flags
  • some work item types are only meaningful at group scope
  • use glab issue for stable day-to-day issue workflows

See: https://docs.gitlab.com/policy/development_stages_support/

Quick start

# List work items in the current project
glab work-items list

# Create a task in the current project
glab work-items create --type task --title "Follow up on flaky pipeline"

# Create or update with a multi-line description from a file
glab work-items create --type task --title "Follow up" --description-file description.md
glab work-items update 42 --description-file description.md

# Attach a project-scoped file reference
glab work-items create --type task --title "Follow up" --attach ./evidence.png
glab work-items update 42 --attach ./latest.png

# Create a group-scoped epic
glab work-items create --type epic --group my-group --title "Platform rewrite"

Scope model

glab work-items uses repository context by default, then lets you override scope explicitly:

  • Current repo context → project work items in the checked-out repository
  • --repo owner/project → a different project
  • --group my-group → group/subgroup work items

This matters because some work item types are commonly project-scoped (task, issue, incident) while others often live at group scope (epic, objective, key_result).

Read the full file on GitHub · 231 lines

Files

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.

Changes

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.

  1. 9d ago Changed · +13 lines 68c8185953d6
  2. 1mo ago Changed · +8 lines 683ac4ad7beb
  3. 2mo ago First seen · 210 lines · 80 tokens per session scan A 262c9b2d815f

Subscribe to this mod's changes

glab-workitems is a skill published in the GitHub repository vince-winkintel/gitlab-cli-skills (49 stars, last pushed today), licensed MIT. It adds 80 tokens to every session and 2,028 once invoked, about $0.0003 per session on Opus 5.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-30.