What is building-devsecops-pipeline-with-gitlab-ci?

A GitLab CI/CD pipeline that runs security checks during software delivery, including source-code, running-application, container, dependency, secret, and licence checks. CI/CD is the automated process that builds, tests, and delivers code.

It helps teams configure GitLab jobs for code scanning, application testing in a staging environment, container and dependency checks, secret detection, and licence compliance.

It finds security weaknesses and exposed secrets earlier, before they reach production. It also brings several security checks into one repeatable workflow.

building-devsecops-pipeline-with-gitlab-ci — Skill for Claude Code and

Install

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.

Any agent

npx skills add autohandai/community-skills --skill building-devsecops-pipeline-with-gitlab-ci

Clone the repo

git clone --depth 1 https://github.com/autohandai/community-skills

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/autohandai/community-skills/building-devsecops-pipeline-with-gitlab-ci/github.svg)](https://agentmods.dev/skills/autohandai/community-skills/building-devsecops-pipeline-with-gitlab-ci)

Your own site

<a href="https://agentmods.dev/skills/autohandai/community-skills/building-devsecops-pipeline-with-gitlab-ci"><img src="https://agentmods.dev/badge/skills/autohandai/community-skills/building-devsecops-pipeline-with-gitlab-ci/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/autohandai/community-skills/building-devsecops-pipeline-with-gitlab-ci"><img src="https://agentmods.dev/badge/skills/autohandai/community-skills/building-devsecops-pipeline-with-gitlab-ci.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,901 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 84% copy Near-identical to another mod in the catalogue.

Token cost

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.00043	$0.01901
Opus 5	$0.00022	$0.00950
Sonnet 5	$0.00009	$0.00380
Haiku 4.5	$0.00004	$0.00190

Measured 8d ago against content hash 21a9949a442a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

building-devsecops-pipeline-with-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 8d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/agent.py, scripts/process.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Origin

This is a copy

84% identical to building-devsecops-pipeline-with-gitlab-ci — 42 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

building-devsecops-pipeline-with-gitlab-ci/SKILL.md · 237 lines

How it starts

The opening of the file, as written. The whole thing — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Building DevSecOps Pipeline with GitLab CI

Overview

GitLab provides an integrated DevSecOps platform that embeds security testing directly into the CI/CD pipeline. By leveraging GitLab's built-in security scanners---SAST, DAST, container scanning, dependency scanning, secret detection, and license compliance---teams can shift security left, catching vulnerabilities during development rather than post-deployment. GitLab Duo AI assists with false positive detection for SAST vulnerabilities, helping security teams focus on genuine issues.

Prerequisites

GitLab Ultimate license (required for full security scanner suite)
GitLab Runner configured (shared or self-hosted)
.gitlab-ci.yml pipeline configuration familiarity
Docker-in-Docker (DinD) or Kaniko for container builds
Application deployed to a staging environment for DAST scanning

Core Security Scanning Stages

Static Application Security Testing (SAST)

SAST analyzes source code for vulnerabilities before compilation. GitLab supports 14+ languages using analyzers such as Semgrep, SpotBugs, Gosec, Bandit, and NodeJsScan. The simplest inclusion uses GitLab's managed templates.

Dynamic Application Security Testing (DAST)

DAST tests running applications by simulating attack payloads against HTTP endpoints. It detects XSS, SQLi, CSRF, and other runtime vulnerabilities that static analysis cannot find. DAST requires a deployed, accessible target URL.

Container Scanning

Uses Trivy to scan Docker images for known CVEs in OS packages and application dependencies. Runs after the Docker build stage to gate images before they reach a registry.

Dependency Scanning

Inspects dependency manifests (package.json, requirements.txt, pom.xml, Gemfile.lock) for known vulnerable versions. Operates at the source code level, complementing container scanning.

Secret Detection

Scans commits for accidentally committed credentials, API keys, tokens, and private keys using pattern matching and entropy analysis. Runs on every commit to prevent secrets from reaching the repository.

Read the full file on GitHub · 237 lines

Files

What ships with it

7 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.

Changes

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.

8d ago First seen · 237 lines · 43 tokens per session scan A 21a9949a442a

Subscribe to this mod's changes

building-devsecops-pipeline-with-gitlab-ci is a skill published in the GitHub repository autohandai/community-skills (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 1,901 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to building-devsecops-pipeline-with-gitlab-ci, differing in 42 lines, and is treated as a copy.

CI and CD Containers DAST DevOps and cloud Security agent-skill agent-skills agentsmd cicd-security coding-agent-skills container-scanning dependency-scanning devsecops gitlab-ci sast secret-detection