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 serejaris/kimi-skills --skill glab-authgit clone --depth 1 https://github.com/serejaris/kimi-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/serejaris/kimi-skills/glab-auth)<a href="https://agentmods.dev/skills/serejaris/kimi-skills/glab-auth"><img src="https://agentmods.dev/badge/skills/serejaris/kimi-skills/glab-auth/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/serejaris/kimi-skills/glab-auth"><img src="https://agentmods.dev/badge/skills/serejaris/kimi-skills/glab-auth.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00093 | $0.00758 |
| Opus 5 | $0.00046 | $0.00379 |
| Sonnet 5 | $0.00019 | $0.00152 |
| Haiku 4.5 | $0.00009 | $0.00076 |
Grade A, and why
glab-auth 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 9d 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 auth
管理 GitLab CLI 认证。
快速开始
# 交互式登录
glab auth login
# 查看当前认证状态
glab auth status
# 登录到其他实例
glab auth login --hostname gitlab.company.com
# 登出
glab auth logout
工作流程
首次设置
- 运行
glab auth login - 选择认证方式（token 令牌或浏览器）
- 按照提示操作，连接你的 GitLab 实例
- 使用
glab auth status验证
切换账户/实例
-
从当前账户登出：
glab auth logout -
登录到新实例：
glab auth login --hostname gitlab.company.com -
验证：
glab auth status
Docker 镜像仓库访问
-
配置 Docker 凭证助手：
glab auth configure-docker -
验证 Docker 是否可以认证：
docker login registry.gitlab.com -
拉取私有镜像：
docker pull registry.gitlab.com/group/project/image:tag
故障排查
"401 Unauthorized"（未授权）错误：
- 检查状态：
glab auth status - 验证 token 是否过期（在 GitLab 设置中查看）
- 重新认证：
glab auth login
多实例场景：
- 使用
--hostname参数指定实例 - 每个实例的认证信息独立维护
Docker 认证失败：
- 重新运行：
glab auth configure-docker - 检查 Docker 配置：
cat ~/.docker/config.json - 确认凭证助手已设置：
"credHelpers": { "registry.gitlab.com": "glab-cli" }
子命令
详细参数文档请参见 references/commands.md：
login- 向 GitLab 实例进行认证logout- 从 GitLab 实例登出status- 查看认证状态configure-docker- 配置 Docker 使用 GitLab 镜像仓库docker-helper- Docker 凭证助手dpop-gen- 生成 DPoP 令牌
相关技能
初始设置：
- 完成认证后，参见
glab-config设置 CLI 默认配置 - 参见
glab-ssh-key进行 SSH 密钥管理 - 参见
glab-gpg-key设置提交签名
仓库操作：
- 参见
glab-repo克隆仓库 - 首次克隆/推送前需要先完成认证
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.
- 9d ago First seen · 105 lines · 93 tokens per session scan A 30e2063c94a0
glab-auth is a skill published in the GitHub repository serejaris/kimi-skills (6 stars, last pushed 1mo ago), licensed MIT. It adds 93 tokens to every session and 758 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
offensive-container-escape
Container escape and breakout techniques targeting Docker, containerd, and Podman runtimes. Covers privileged container breakout via host filesystem mount and nsenter, Docker socket abuse through /var/run/docker.sock, Linux capability exploitation including CAPSYSADMIN, CAPSYSPTRACE, and CAPNETADMIN, cgroup v1…
resolve-pr-comments
Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments. Handles both change requests (fix or skip) and reviewer questions (explain using reasoning recalled from past Claude Code transcripts). Use when the user asks to "resolve PR comments", "fix review comments", "address PR…
create-pr
Create a GitHub pull request with a drafted title and description. Use when the user asks to "create a PR", "create a pull request", "open a PR", or "submit a PR".
update-pr
Update an existing GitHub pull request's title and description to reflect the current state of the branch. Use when the user asks to "update the PR", "update PR description", "update PR title", "refresh PR description", or "sync PR with changes".
changelog-rules
Shared changelog conventions and formatting rules referenced by /create-changelog and /update-changelog. Not typically invoked directly.
fetch-pr-comments
Fetch and summarize review feedback and conversation from a GitHub PR (unresolved review threads, review bodies, and PR conversation comments) without making changes. Use when the user asks to "fetch PR comments", "show PR comments", "check PR for unresolved comments", "list review comments", "what comments are on the…