# CI/CD Pipeline Secrets Exposure

> Detects secrets hardcoded in CI/CD configuration files (GitLab CI, GitHub Actions, CircleCI, Jenkins).

- Skill: `zakirkun/ci-cd-pipeline-secrets-exposure` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add zakirkun/ci-cd-pipeline-secrets-exposure`
- Raw SKILL.md: https://api.skillmd.com/api/skills/zakirkun/ci-cd-pipeline-secrets-exposure/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: zakirkun (https://skillmd.com/u/zakirkun)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/zakirkun/ci-cd-pipeline-secrets-exposure

---


# CI/CD Pipeline Secrets Exposure

## Overview
CI/CD configuration files committed to version control often contain hardcoded API keys, tokens, or passwords. These are frequently visible in:
- Public repositories
- Git history (even after removal)
- Third-party services that access the repository

## Remediation
- Use CI/CD secret management (GitHub Secrets, GitLab CI Variables, CircleCI Contexts)
- Reference secrets as `${{ secrets.MY_SECRET }}` or `$MY_VAR`
- Scan git history with tools like `trufflehog` or `gitleaks`