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 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/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/cookiemonsterdev/agents-skills/gitlab-ci-docs"><img src="https://agentmods.dev/badge/skills/cookiemonsterdev/agents-skills/gitlab-ci-docs.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.01216 |
| Opus 5.5 | $0.00037 | $0.00486 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (6 stars, last pushed today), licensed MIT. It adds 93 tokens to every session and 1,216 once invoked, about $0.0004 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-31.
Other skills, from other repositories
ci-cd-and-automation
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
google-cloud-slo-alert-configuration
Configures Cloud Monitoring PromQL-based Service Level Objective (SLO) alerting policies on Google Cloud for resources registered in App Hub or individually specified. Generates Terraform output. Use when the user asks to configure an SLO or Service Level Objective. Don't use for standard alerting policies.
cloud-build-basics
Teaches the fundamentals of Cloud Build on Google Cloud. 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.
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.
factory
Experimental workflow for configuring an autonomous software delivery factory. Use when choosing feedback sources, schedules, worktree behavior, autonomy gates, or host automations.
gh-fix-ci
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use gh to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.