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-deploy-keygit 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-deploy-key)<a href="https://agentmods.dev/skills/vince-winkintel/gitlab-cli-skills/glab-deploy-key"><img src="https://agentmods.dev/badge/skills/vince-winkintel/gitlab-cli-skills/glab-deploy-key/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-deploy-key"><img src="https://agentmods.dev/badge/skills/vince-winkintel/gitlab-cli-skills/glab-deploy-key.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.00059 | $0.00381 |
| Opus 5.5 | $0.00024 | $0.00152 |
| Sonnet 5.5 | $0.00012 | $0.00076 |
| Haiku 4.5 | $0.00006 | $0.00038 |
Grade A, and why
glab-deploy-key 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 2mo 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 deploy-key
Overview
Manage deploy keys.
USAGE
glab deploy-key <command> [command] [--flags]
COMMANDS
add [key-file] [--flags] Add a deploy key to a GitLab project.
delete <key-id> Deletes a single deploy key specified by the ID.
get <key-id> Returns a single deploy key specified by the ID.
list [--flags] Get a list of deploy keys for the current project.
FLAGS
-h --help Show help for this command.
-R --repo Select another repository. Can use either `OWNER/REPO` or `GROUP/NAMESPACE/REPO` format. Also accepts full URL or Git URL.
Quick start
glab deploy-key --help
Structured output
glab deploy-key list and glab deploy-key get support --output json / -F json for structured output, which is useful for agent automation.
# List deploy keys with JSON output
glab deploy-key list --output json
glab deploy-key list -F json
# Get a specific deploy key with JSON output
glab deploy-key get <key-id> --output json
glab deploy-key get <key-id> -F json
Subcommands
See references/commands.md for full --help output.
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.
- 2mo ago First seen · 48 lines · 59 tokens per session scan A 7cbb2fce5a02
glab-deploy-key is a skill published in the GitHub repository vince-winkintel/gitlab-cli-skills (49 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 381 once invoked, about $0.0002 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
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.
start-temps-cluster
Start (or restart) a local multi-node Temps cluster using Docker-in-Docker — one control plane + 3 worker nodes, each a privileged DinD container running its own dockerd + temps agent, wired with the real multi-host overlay (VXLAN, computecidr allocation) via tools/dev-cluster/ in whichever checkout/worktree you run…
pr-watch
Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.