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 selvarajmurugesan90/ops-engineering-skills --skill gitlab-cicd-pipeline-designgit clone --depth 1 https://github.com/selvarajmurugesan90/ops-engineering-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/selvarajmurugesan90/ops-engineering-skills/gitlab-cicd-pipeline-design)<a href="https://agentmods.dev/skills/selvarajmurugesan90/ops-engineering-skills/gitlab-cicd-pipeline-design"><img src="https://agentmods.dev/badge/skills/selvarajmurugesan90/ops-engineering-skills/gitlab-cicd-pipeline-design/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/selvarajmurugesan90/ops-engineering-skills/gitlab-cicd-pipeline-design"><img src="https://agentmods.dev/badge/skills/selvarajmurugesan90/ops-engineering-skills/gitlab-cicd-pipeline-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 25 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 241 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 315 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 317 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00105 | $0.03052 |
| Opus 5 | $0.00053 | $0.01526 |
| Sonnet 5 | $0.00021 | $0.00610 |
| Haiku 4.5 | $0.00011 | $0.00305 |
Grade A, and why
gitlab-cicd-pipeline-design 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 12d 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 — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitLab CI/CD Pipeline Design
Purpose
GitLab CI/CD pipelines are defined entirely in one file, .gitlab-ci.yml,
executed by GitLab Runners (shared, group, or project-specific) against a
stages:/rules: model that differs in specifics from GitHub Actions or
Jenkins even though the underlying pipeline concepts overlap (see
ci-cd-pipeline-design
for the vendor-neutral version). This skill covers GitLab-specific
mechanics: the stages:/rules: trigger model (and why rules: has
superseded the legacy only:/except:), include: for sharing pipeline
templates across projects, and runner/executor configuration
specifics.
When to use
- A project needs its first
.gitlab-ci.yml, or an existing one has a job that isn't running (or runs) when expected. - Migrating legacy
only:/except:job keywords to the modernrules:syntax. - Sharing pipeline logic across multiple projects via
include:(local, project, remote, or template includes) rather than duplicating YAML. - Diagnosing why a job is stuck
pending(no runner picks it up) or fails only on certain runners. - Designing merge-request pipelines (
merge_request_event) alongside branch/tag pipelines without running both redundantly on the same commit.
Prerequisites & environment
- GitLab 15+ recommended: the
rules:keyword and modernworkflow:block are fully mature from GitLab 13+, but 15+ is assumed here for current defaults and deprecation warnings aroundonly:/except:. - At least one available GitLab Runner registered against the project,
group, or instance, with an executor type understood (
shell,docker,docker+machine,kubernetes) — jobtags:must match a runner's configured tags or the job stayspendingforever. - Project or group maintainer access to configure CI/CD variables (Settings → CI/CD → Variables, marked "Protected"/"Masked" as appropriate) and to register runners.
- For
include:of remote/template files: network access from the GitLab instance to the include source (forinclude: remote:), or access to the referenced project (forinclude: project:).
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.
- 12d ago First seen · 318 lines · 105 tokens per session scan A 65d13439678b
gitlab-cicd-pipeline-design is a skill published in the GitHub repository selvarajmurugesan90/ops-engineering-skills (39 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 105 tokens to every session and 3,052 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-30.
Other skills, from other repositories
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
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.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.