- Home
- Skills
- DevOps & Cloud
- GitLab CI Safety Check
More screenshots
Works with the AI Agents you already use
GitLab CI Safety Check
It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach.
$5
GitLab CI Safety Check
Example session with this skill installed
Check this project with gitlab-ci-safety-check.
- Read your context and instructions
- Compiled the gitlab ci safety
$ python3 scripts/check_gitlab.py examples/risky
BLOCK .gitlab-ci.yml:6 G01 SECRET_IN_VARIABLES
API_TOKEN=<redacted, 21 chars>
Why: A password, token or key is written as a literal value under variables:, so everyone who can read the repository can use it, and it stays in git history.
Safer: Rotate it, then store it as a masked and protected CI/CD variable in Settings > CI/CD > Variables (or in a secrets manager) and refer to it as $NAME.
BLOCK .gitlab-ci.yml:14 G02 CURL_PIPE_TO_SHELL
BLOCK .gitlab-ci.yml:17 G03 SECRET_PRINTED_TO_LOG
BLOCK .gitlab-ci.yml:22 G04 SECRET_FILE_IN_ARTIFACTS
REVIEW .gitlab-ci.yml:3 G12 INCLUDE_NOT_PINNED
REVIEW .gitlab-ci.yml:7 G14 TLS_CHECK_DISABLED
REVIEW .gitlab-ci.yml:9 G11 IMAGE_NOT_PINNED
REVIEW .gitlab-ci.yml:16 G15 ENVIRONMENT_DUMPED
REVIEW .gitlab-ci.yml:26 G11 IMAGE_NOT_PINNED
REVIEW .gitlab-ci.yml:29 G13 SECURITY_JOB_ALLOWED_TO_FAIL
REVIEW .gitlab-ci.yml:36 G16 PRODUCTION_DEPLOY_NOT_RESTRICTED
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 1 file, 1 with GitLab CI content.
This is a static check of file text. NOT FLAGGED is not a guarantee.
Connects securely to your tools. The creator never sees your data.
About this skill
An echo "$API_TOKEN" in a script puts the token in the job log, and a .env file listed under artifacts can be downloaded by anyone who can see the pipeline. This skill finds those and eight other GitLab CI risks, and tells you how to fix each one.
Your agent runs a scanner on .gitlab-ci.yml, *.gitlab-ci.yml files and the YAML under .gitlab/. It reads global settings, default:, hidden jobs and every job, follows YAML anchors and extends, and skips !reference lines. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secret values are never printed.
What it checks
BLOCK
- G01: a password, token or key written in variables
- G02: curl or wget piped into a shell
- G03: a secret variable echoed to the job log
- G04: a .env file, private key or Terraform state kept as an artifact
REVIEW
- G11: an image or service with no tag or :latest
- G12: an include from a URL, or a project or component not pinned to a tag
- G13: a security scan job with allow_failure: true
- G14: TLS checks turned off (curl -k, GIT_SSL_NO_VERIFY)
- G15: env or printenv dumping every variable to the log
- G16: a production deploy job with no rules, only or manual step
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason and safer approach for each rule
- A risky and a safe example pipeline, and the real report the scanner produces on the risky one
Limits It reads each file on its own and does not fetch included files or see CI/CD variables set in GitLab settings. NOT FLAGGED is not a guarantee.
Static check of CI YAML. Included files are not fetched, and masked or protected settings in GitLab are not visible. NOT FLAGGED is not a guarantee.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 5 days ago
Requires
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example pipeline includes a clearly fake, inert token (not-a-real-token-1234) for the scanner to find.