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 agentmods add skills/cookiemonsterdev/agents-skills/gitlab-ci-docsnpx skills add cookieMonsterDev/agents-skills --skill gitlab-ci-docsgit clone --depth 1 https://github.com/cookieMonsterDev/agents-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/cookiemonsterdev/agents-skills/gitlab-ci-docs)<a href="https://agentmods.dev/skills/cookiemonsterdev/agents-skills/gitlab-ci-docs"><img src="https://agentmods.dev/badge/skills/cookiemonsterdev/agents-skills/gitlab-ci-docs.svg" alt="Measured on agentmods" 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 | $0.00093 | $0.01216 |
| Opus 5 | $0.00046 | $0.00608 |
| Sonnet 5 | $0.00019 | $0.00243 |
| Haiku 4.5 | $0.00009 | $0.00122 |
Grade A, and why
gitlab-ci-docs 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 3d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitLab CI/CD questions are easy to answer from stale memory or GitHub Actions assumptions. Use this skill to ground answers in official GitLab documentation and return the closest authoritative page instead of generic CI/CD advice.
When to Use
Use this skill when the request is about:
- GitLab CI/CD concepts, terminology, or product boundaries
.gitlab-ci.ymlsyntax, stages, jobs, rules, needs, extends, include, or workflow keywords- GitLab-hosted runners, self-managed runners, project runners, or runner configuration
- CI/CD variables, predefined variables, inputs, expressions, or pipeline-level configuration
- Artifacts, caches, reports, dependencies, and job outputs
- Environments, deployments, review apps, and deployment tiers
- CI/CD components, the CI/CD Catalog, reusable pipeline configuration, or
include:component - Parent-child pipelines, multi-project pipelines, merge request pipelines, merge trains, or pipeline schedules
- Pipeline security, secrets management, external secrets, masked/protected variables, or ID tokens
- Migrating to or from GitLab CI/CD, or comparing GitLab CI/CD with other CI systems
- Troubleshooting pipeline behavior when the user needs documentation, syntax guidance, or official references
Do not use this skill for:
- GitHub Actions workflows, runners, or YAML. Use
github-actions-docs. - GitLab repository, merge request, or project administration unrelated to CI/CD. Search GitLab docs outside the CI/CD section.
- A specific failing pipeline log or CI failure triage in this repository when another skill such as
gh-fix-ciis the sharper fit for GitHub-hosted checks.
Workflow
1. Classify the request
Decide which bucket the question belongs to before searching:
- Getting started, tutorials, and pipeline concepts
- YAML syntax and pipeline configuration
- Runners and execution environment
- Variables, inputs, and expressions
- Artifacts, caches, and job dependencies
- Environments and deployments
- CI/CD components and reusable configuration
- Security, secrets, and pipeline hardening
- Advanced pipeline types and orchestration
- Monitoring, debugging, and troubleshooting
What ships with it
2 files 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.
- 3d ago First seen · 105 lines · 93 tokens per session scan A d6b6a3f0fba4
gitlab-ci-docs is a skill published in the GitHub repository cookieMonsterDev/agents-skills (4 stars, last pushed 14d ago), licensed MIT. It adds 93 tokens to every session and 1,216 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-08-31.
Other skills, from other repositories
comet-github-ci-triage
使用 PR 当前准确 head、失败 job 日志、本地复现边界和可合并状态，诊断 Comet PR 的 GitHub Actions 与覆盖率检查。PR 出现 CI 报错、Codecov 问题、过期检查或无法解释的红色 job 时使用。.
aws-cloudformation-task-ecs-deploy-gh
Provides patterns to deploy ECS tasks and services with GitHub Actions CI/CD. Use when building Docker images, pushing to ECR, updating ECS task definitions, deploying ECS services, integrating with CloudFormation stacks, configuring AWS OIDC authentication for GitHub Actions, and implementing production-ready…
pentest-supply-chain
Software supply chain security — dependency confusion, CI/CD pipeline attacks, lockfile integrity, and build artifact verification.
glab-cli
GitLab CLI (glab) reference and workflow for repository, merge request, issue, CI/CD, release, and API operations across GitLab.com and self-managed or dedicated instances. Use when Codex needs to run or explain glab commands, usually by relying on the current glab context first, and only falling back to git remote -v…
zb-release-pipeline
Generate a GitHub Actions pipeline that builds a zb (Zero Dependencies Builder) project and publishes a GitHub Release with the produced JAR. Use whenever the user wants CI/CD, a build pipeline, a release workflow, or GitHub Actions for a zb-based Java project — phrases like "set up GitHub Actions for this zb…
fastly-fiddle
Use when testing VCL against real Fastly edge infrastructure, writing assertion-based Fiddle tests, producing shareable fiddle URLs for bug reproductions, running VCL integration tests in CI, linting VCL remotely via the Fiddle API, or working with clientFetch/events/originFetches test expressions.