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-runner-controllergit 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-runner-controller)<a href="https://agentmods.dev/skills/serejaris/kimi-skills/glab-runner-controller"><img src="https://agentmods.dev/badge/skills/serejaris/kimi-skills/glab-runner-controller/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-runner-controller"><img src="https://agentmods.dev/badge/skills/serejaris/kimi-skills/glab-runner-controller.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.00073 | $0.01957 |
| Opus 5 | $0.00036 | $0.00979 |
| Sonnet 5 | $0.00015 | $0.00391 |
| Haiku 4.5 | $0.00007 | $0.00196 |
Grade A, and why
glab-runner-controller 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.
How it starts
The opening of the file, as written. The whole thing — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
glab-runner-controller
管理 GitLab Runner 控制器及其认证令牌。
⚠️ 实验性功能
状态: 实验性(仅管理员可用)
- 此功能可能在没有事先通知的情况下被破坏或移除
- 使用风险自担
- 需要 GitLab 管理员权限
- 参阅:https://docs.gitlab.com/policy/development_stages_support/
功能说明
Runner 控制器用于管理基础设施中 GitLab Runner 的编排。此技能提供以下命令:
- 创建和配置 Runner 控制器
- 管理控制器生命周期(列出、更新、删除)
- 生成和轮换认证令牌
- 撤销已泄露的令牌
常见工作流
创建 Runner 控制器
# 使用默认设置创建
glab runner-controller create
# 创建时添加描述
glab runner-controller create --description "Production runners"
# 创建已启用的控制器
glab runner-controller create --description "Prod" --state enabled
状态说明:
disabled- 控制器已创建但未激活enabled- 控制器已激活(默认)dry_run- 测试模式(不实际执行 Runner)
列出和查看控制器
# 列出所有控制器
glab runner-controller list
# 分页列出
glab runner-controller list --page 2 --per-page 50
# 以 JSON 格式输出
glab runner-controller list --output json
更新控制器
# 更新描述
glab runner-controller update 42 --description "Updated name"
# 更改状态
glab runner-controller update 42 --state disabled
# 同时更新描述和状态
glab runner-controller update 42 --description "Prod" --state enabled
删除控制器
# 删除(会有确认提示)
glab runner-controller delete 42
# 跳过确认直接删除
glab runner-controller delete 42 --force
令牌管理工作流
令牌生命周期
创建 → 轮换 → 撤销 是安全最佳实践中的典型令牌生命周期。
1. 创建令牌
# 为控制器 42 创建令牌
glab runner-controller token create 42
# 创建时添加描述
glab runner-controller token create 42 --description "production"
# 以 JSON 格式输出(便于自动化)
glab runner-controller token create 42 --output json
重要: 令牌值创建后只显示一次,请立即保存。
2. 列出令牌
# 列出控制器 42 的所有令牌
glab runner-controller token list 42
# 以 JSON 格式列出
glab runner-controller token list 42 --output json
# 分页查看
glab runner-controller token list 42 --page 1 --per-page 20
3. 轮换令牌
轮换操作会生成新令牌并使旧令牌失效。
# 轮换令牌 1(带确认提示)
glab runner-controller token rotate 42 1
# 跳过确认直接轮换
glab runner-controller token rotate 42 1 --force
# 轮换并以 JSON 格式输出
glab runner-controller token rotate 42 1 --force --output json
适用场景:
- 定期轮换(满足安全策略要求)
- 令牌泄露后的响应
- 员工离职前的密钥轮换
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 · 258 lines · 73 tokens per session scan A 58cbdfc3b5c4
glab-runner-controller is a skill published in the GitHub repository serejaris/kimi-skills (6 stars, last pushed 1mo ago), licensed MIT. It adds 73 tokens to every session and 1,957 once invoked, about $0.0004 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
neo-azure-pipelines
Use this skill when the user asks to create, review, debug, or modernize Azure Pipelines YAML for CI/CD, especially .NET builds, Azure App Service deploys, or IIS/on-premises deploys. Prefer bundled templates and verify task syntax against Microsoft docs when version-specific accuracy matters.
cloud-build-basics
Teaches the fundamentals of Google Cloud Build (GCB). Covers core concepts, API enablement, console navigation to the Build History page, and the end-to-end workflow for creating and manually running a basic build trigger. Do not use for managing private pools or complex pipeline architectures.
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…
offensive-cloud
Cloud security attack methodology covering AWS, Azure, and GCP. Includes credential harvesting (IMDS, /.aws, env vars, leaked CI secrets, instance roles), enumeration with cloud-specific tools (pacu, ScoutSuite, Prowler, ROADtools, gcpenum), privilege escalation paths (IAM PassRole, AssumeRole chains, Lambda/Functions…
review-tooling
Detect what dev tooling infrastructure a project has and flag gaps across linters, formatters, pre-commit hooks, test runners, and CI/CD pipelines. Returns structured findings without applying changes. Use when the user asks to "review tooling", "check project tooling", "what tooling is missing", "review dev…
coolify-operator
Master Coolify operator for self-hosted deployment platform. Use when the user mentions 'coolify', 'deploy on coolify', 'list/restart/redeploy applications', 'view coolify logs', 'coolify API/CLI', 'manage coolify servers/databases/apps', or 'coolify context'. Automates deployments and management via REST API or…