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-duogit 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-duo)<a href="https://agentmods.dev/skills/vince-winkintel/gitlab-cli-skills/glab-duo"><img src="https://agentmods.dev/badge/skills/vince-winkintel/gitlab-cli-skills/glab-duo/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-duo"><img src="https://agentmods.dev/badge/skills/vince-winkintel/gitlab-cli-skills/glab-duo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 40 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 47 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00074 | $0.00828 |
| Opus 5.5 | $0.00030 | $0.00331 |
| Sonnet 5.5 | $0.00015 | $0.00166 |
| Haiku 4.5 | $0.00007 | $0.00083 |
Grade A, and why
glab-duo 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 23d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
glab duo
Overview
glab duo is centered on the GitLab Duo Agent Platform. The current visible command surface exposes glab duo cli; the legacy glab duo ask command is hidden and deprecated.
Quick start
glab duo --help
Command surface guidance
Upstream glab now hides and deprecates glab duo ask.
Treat glab duo ask as legacy guidance only for older installed versions that still expose it in live help. For current forward-looking documentation, prefer:
glab duo cli
Use glab duo cli for the forward-looking GitLab Duo Agent Platform experience. glab handles authentication for the Duo CLI after you authenticate once with glab auth login.
Prerequisites for the GA path are GitLab 19.2 or later and the GitLab Duo Agent Platform prerequisites. GitLab Self-Managed and Dedicated instances must also allow Duo CLI access. GitLab 18.11 through 19.1 require beta and experimental features to be enabled.
Installing GitLab Duo CLI
glab duo cli supports install, update, and non-interactive confirmation flags. Prefer the explicit update subcommand; --update remains equivalent:
# Install GitLab Duo CLI interactively
glab duo cli --install
# Install GitLab Duo CLI non-interactively (auto-confirm)
glab duo cli --install --yes
# Check for and install a compatible Duo CLI update
glab duo cli update
# Legacy-equivalent flag form
glab duo cli --update
Use --install to download and install the GitLab Duo CLI binaries. Use --yes to skip confirmation prompts during installation, which is useful for automation and CI/CD pipelines. Updates stay within the major version supported by the installed glab release; update glab first when Duo reports a newer major version. The update command does not replace a custom binary configured through GLAB_DUO_CLI_BINARY_PATH or duo_cli_binary_path.
Interactive and headless modes
# Interactive, multi-prompt session with build and plan modes
glab duo cli
# One bounded prompt for a runner, script, or automated workflow
glab duo cli run --goal "Fix the failing tests in this project"
# Wrapper help versus the installed Duo CLI's own command surface
glab duo cli --help
glab duo cli help
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.
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.
- 23d ago Changed · +3 lines 1b65967dde67
- 2mo ago First seen · 76 lines · 74 tokens per session scan A 2a083aec2a8f
glab-duo is a skill published in the GitHub repository vince-winkintel/gitlab-cli-skills (49 stars, last pushed today), licensed MIT. It adds 74 tokens to every session and 828 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.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…