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-configgit 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-config)<a href="https://agentmods.dev/skills/vince-winkintel/gitlab-cli-skills/glab-config"><img src="https://agentmods.dev/badge/skills/vince-winkintel/gitlab-cli-skills/glab-config/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-config"><img src="https://agentmods.dev/badge/skills/vince-winkintel/gitlab-cli-skills/glab-config.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
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 →
- high Privilege Escalation · line 20 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 115 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Rogue Agent · line 97 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Privilege Escalation · line 109 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
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.00051 | $0.02811 |
| Opus 5.5 | $0.00020 | $0.01124 |
| Sonnet 5.5 | $0.00010 | $0.00562 |
| Haiku 4.5 | $0.00005 | $0.00281 |
Grade B, and why
glab-config scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
Keep these env files outside version control, restrict their permissions (for example `chmod 600`), be mindful of backup exposure, and use least-privilege bot/service-account tokens. How it starts
The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
glab config
Host selection and output rendering
The configured host key is a fallback, not a constraint on repository remotes. Inside a repository, a remote on another host can select that host. Environment host selectors (GITLAB_HOST, GITLAB_URI, GL_HOST, or the corresponding CI auto-login source) remain authoritative; no matching remote produces an error rather than silently switching hosts. Explicit full-URL repository selectors carry their own host. This host-selection rule is separate from normal setting precedence: environment values, non-empty per-host settings/eligible keyring credentials, local config, global config, then defaults.
Global output color is controlled by GLAB_COLOR=auto|never|always or the global color config key. always/never override NO_COLOR; auto detects terminal output and honors legacy color environment behavior. There is no global --color CLI flag. glab mr diff --color is a separate command-specific option; label color flags set label metadata. For credential-free, uncolored help use GLAB_COLOR=never glab help <command>.
glamour_style defaults to auto and detects the terminal background; explicit dark, light, notty, and custom styles remain available. Existing seeded dark defaults can migrate once to auto; use an explicit environment style override when deterministic rendering matters. Help retains Fang's indented uppercase headings and can wrap or truncate examples. Preserve exact help output when capturing references, and use supported JSON output rather than parsing terminal formatting. Error text is displayed as written, so punctuation is not a stable parsing contract.
Overview
Authored synopsis (not a binary capture). The complete captured help, including per-key environment aliases, scope, and warnings, is in references/commands.md.
- Global behavior:
branch_prefix,browser,check_update,color,debug,display_hyperlinks,duo_cli_auto_download,duo_cli_auto_run,editor,git_protocol,glab_pager,glamour_style,host,no_prompt,notify_skill_updates,orbit_cli_auto_download,orbit_cli_auto_run,remote_alias,show_whats_new, andtelemetry. - Per-host behavior:
api_host,api_protocol,artifact_registry_domains,ca_cert,client_cert,client_id,client_key,container_registry_domains,custom_headers,job_token,proxy,skip_tls_verify,ssh_host,subfolder,token, anduse_keyring. Select these with--host <hostname>. - Use canonical keys in new automation. Accepted compatibility aliases and their environment-variable precedence are documented below and in the full reference.
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.
- 2d ago Changed · +13 lines 088277536788
- 23d ago Changed 216098d21fb0
- 1mo ago Changed · +18 lines bed578500a01
- 1mo ago Changed · -5 lines e163577e28f4
- 2mo ago First seen · 174 lines · 51 tokens per session scan B 41617ebec634
glab-config is a skill published in the GitHub repository vince-winkintel/gitlab-cli-skills (49 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 2,811 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.