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-whatsnewgit 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-whatsnew)<a href="https://agentmods.dev/skills/vince-winkintel/gitlab-cli-skills/glab-whatsnew"><img src="https://agentmods.dev/badge/skills/vince-winkintel/gitlab-cli-skills/glab-whatsnew/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-whatsnew"><img src="https://agentmods.dev/badge/skills/vince-winkintel/gitlab-cli-skills/glab-whatsnew.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.00069 | $0.00489 |
| Opus 5 | $0.00034 | $0.00244 |
| Sonnet 5 | $0.00014 | $0.00098 |
| Haiku 4.5 | $0.00007 | $0.00049 |
Grade A, and why
glab-whatsnew 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 10d 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.
What it actually says
glab whatsnew
View GitLab CLI release notes from the terminal.
Quick start
# Show release notes since the last viewed/post-upgrade baseline, capped at 10 releases
glab whatsnew
# Show notes for the latest published release
glab whatsnew --latest
# Show notes for a specific release
glab whatsnew v1.102.0
# Show notes for every release after a baseline
glab whatsnew --since v1.100.0
When to use
Use glab whatsnew after upgrading glab or before updating automation that depends on command behavior. It is the quickest CLI-native path for inspecting upstream release notes without opening a browser.
Behavior notes
- With no arguments,
glab whatsnewshows releases published since the last time you ranwhatsnewor saw the post-upgrade banner. - The implicit history is capped at the most recent 10 releases.
- Use
--since <version>for deterministic automation or review work where you need an explicit baseline. - Use
--latestwhen you only care about the latest published release.
Agent workflow
# Review all releases newer than the skill repo's last processed glab baseline
glab whatsnew --since v1.100.0
# Then inspect command help for any relevant new/changed command surfaces
glab repo prune --help
glab mr note create --help
glab stack sync --help
Do not treat release-note prose alone as a contract. For skill updates, verify changed command surfaces with glab <command> --help or upstream docs/source before editing guidance.
Command reference
glab whatsnew [version] [--flags]
Flags:
--latest Show release notes for the latest published release only
--since Show release notes for every release newer than this version
-h --help Show help for this command
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.
- 10d ago First seen · 61 lines · 69 tokens per session scan A 9a7a48924858
glab-whatsnew is a skill published in the GitHub repository vince-winkintel/gitlab-cli-skills (47 stars, last pushed 8d ago), licensed MIT. It adds 69 tokens to every session and 489 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-08-30.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
updater_guide
Guidance for checking for and installing Row-Bot updates.