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 G1Joshi/Agent-Skills --skill gitlab-cigit clone --depth 1 https://github.com/G1Joshi/Agent-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/g1joshi/agent-skills/gitlab-ci)<a href="https://agentmods.dev/skills/g1joshi/agent-skills/gitlab-ci"><img src="https://agentmods.dev/badge/skills/g1joshi/agent-skills/gitlab-ci.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.1 | $0.00020 | $0.00453 |
| Opus 5 | $0.00010 | $0.00227 |
| Sonnet 5 | $0.00004 | $0.00091 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
gitlab-ci 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 4d 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
GitLab CI/CD
GitLab CI/CD is known for its robust pipeline definition (.gitlab-ci.yml) and Auto DevOps capabilities. In 2025, CI Components replace legacy templates for modular pipeline composition.
When to Use
- GitLab Users: It's integrated and excellent.
- Complex Pipelines: The DAG (Directed Acyclic Graph) capabilities are sophisticated (
needskeyword). - On-Prem: Excellent support for air-gapped instances.
Quick Start
# .gitlab-ci.yml
stages:
- build
- test
build-job:
stage: build
image: node:20
script:
- npm ci
- npm run build
artifacts:
paths:
- dist/
test-job:
stage: test
image: node:20
script:
- npm test
needs: [build-job]
Core Concepts
.gitlab-ci.yml
The heart of the pipeline. Defines stages, jobs, and environment variables.
Runners
The agents that run jobs. Unique feature: Docker-in-Docker support is first-class (using services: docker:dind).
CI Components (2025)
Reusable pipeline parts listed in the CI Catalog. Replaces the old include: template method with versioned, input-driven components.
Best Practices (2025)
Do:
- Use CI Components: Adopt the module catalog.
- Use
rules: Control when jobs run (e.g., only on Merge Requests, or only whenpackage.jsonchanges). - Use
cachevsartifacts: Usecachefor dependencies (node_modules) andartifactsfor output binaries passed between stages.
Don't:
- Don't use
only/except: They are deprecated. Userules.
References
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.
- 4d ago First seen · 71 lines · 20 tokens per session scan A 409c6e079499
gitlab-ci is a skill published in the GitHub repository G1Joshi/Agent-Skills (12 stars, last pushed 6mo ago), licensed MIT. It adds 20 tokens to every session and 453 once invoked, about $0.0001 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
ci-cd-pipelines
When designing GitHub Actions workflows, optimizing pipeline speed, implementing deployment gates.
general-dev-tools
Core development tools used across any project — git, docker, make, CI/CD, linting, formatting, pre-commit hooks.
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
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.
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.
conductor-revert
Reverts previous work (tracks, phases, or tasks) by identifying associated commits and performing Git reverts.