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 vince-winkintel/gitlab-cli-skills --skill glab-issuegit clone --depth 1 https://github.com/vince-winkintel/gitlab-cli-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/vince-winkintel/gitlab-cli-skills/glab-issue)<a href="https://agentmods.dev/skills/vince-winkintel/gitlab-cli-skills/glab-issue"><img src="https://agentmods.dev/badge/skills/vince-winkintel/gitlab-cli-skills/glab-issue/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/vince-winkintel/gitlab-cli-skills/glab-issue"><img src="https://agentmods.dev/badge/skills/vince-winkintel/gitlab-cli-skills/glab-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00089 | $0.02439 |
| Opus 5.5 | $0.00036 | $0.00976 |
| Sonnet 5.5 | $0.00018 | $0.00488 |
| Haiku 4.5 | $0.00009 | $0.00244 |
Grade A, and why
glab-issue 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 2d 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
glab issue
Create, view, update, and manage GitLab issues.
Open-item selection
glab issue list defaults to open items. Omit the obsolete --opened flag; use --closed or --all for those scopes. This applies to the shared issue/incident list command, including its ls alias, and is separate from MR state selectors.
Template selection
For create --template, a bare name (with optional .md) resolves under the repository's .gitlab/issue_templates/ directory. An absolute path or a path containing a separator is read directly; relative paths use the current directory and ~/ is supported. Use ./template.md for a file in the current directory, rather than a bare template name. A missing template directory means no templates; other directory-listing failures are surfaced and should be repaired before retrying. Read and approve the file contents before posting them; --description-file remains mutually exclusive with --template.
Assignment, dates, and internal notes
issue list --assignee @none selects unassigned issues; --assignee @any selects assigned issues, while @me selects your issues. Date filters are --created-after, --created-before, --updated-after, and --updated-before, with RFC 3339 timestamps including the timezone. Group listing preserves --confidential and --iteration filters.
glab issue list --assignee @none --updated-after 2026-10-01T00:00:00Z
glab issue note 123 --internal --message "Investigation details for project members"
--internal requests an internal note visible only to project members; confirm the target and audience before posting, and never include credentials. issue view displays human-readable time spent and estimated time when available; prefer JSON for automation.
Quick start
# Create an issue
glab issue create --title "Fix login bug" --label bug
# Create or update with a multi-line description from a file
glab issue create --title "Fix login bug" --description-file description.md
glab issue update 123 --description-file description.md
# Upload a screenshot and append its Markdown reference
glab issue create --title "Fix login bug" --description "See below." --attach ./repro.png
glab issue update 123 --attach ./after.png
# List open issues
glab issue list --state opened
# Stable machine-readable output
glab issue list --output json
# View issue details
glab issue view 123
# View or comment on an issue/work item from a GitLab URL
glab issue view https://gitlab.com/group/project/-/work_items/123
glab issue note https://gitlab.com/group/project/-/issues/123 -m "Working on this now"
# Add comment
glab issue note 123 -m "Working on this now"
# Close issue
glab issue close 123
What ships with it
3 files 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.
- 2d ago Changed · +4 lines 93549285ed6c
- 9d ago Changed · +15 lines 83760420ba41
- 16d ago Changed · +16 lines 34aa769df61b
- 23d ago Changed · +5 lines 99d1588d6019
- 1mo ago Changed · +11 lines bd51ee85882b
- 2mo ago First seen · 186 lines · 89 tokens per session scan A 449bdd556049
glab-issue is a skill published in the GitHub repository vince-winkintel/gitlab-cli-skills (49 stars, last pushed today), licensed MIT. It adds 89 tokens to every session and 2,439 once invoked, about $0.0004 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.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.